Automate & Collaborate to Improve Velocity

Multiple Agile projects, linked issues and any relationships between issues are easy to visualize in Structure. View aggregated progress, time and other values at all levels.

Use grouping, sorting, filtering and other rules to build dynamic structures that update in real time as you, your colleagues and other teams work on issues.

More details

Structure helps Atlassian's largest customers visualize, track and manage progress across Jira projects and teams. It does this with adaptable, user-defined, issue hierarchies presented in a familiar spreadsheet-like view of Jira issues. In addition, structures may contain folders and other helpful organizational elements not found in Jira.

"Due to the nature of our business we may have over fifty thousand issues across 5-10 projects running in parallel with shared resources. For us, Structure is essential for organizing these issues in a way that allows us to manage them effectively and get the job done."

Resources

Reviews for cloud

Great tool. We are testing this for a month and would like to use it as our PPM tool. One concern about the progress, based on our testing ,all the columns are still configurable even we only assign view permission to people. Then in that way everyone will see different columns and different progress. Is there any way to lock down the columns and configurations?

Regarding the columns configuration, users can *adjust* what they are seeing, but they will not be able to overwrite the view shared with other people. You can tell that a view is adjusted by spotting a "*" symbol near the view name. You can also revert to the saved view. By design, there's no way to restrict users from adding more columns or changing column configuration.

Also, you can use Perspectives to get a URL that always opens in a predefined configuration.

Feel free to reach us at support@almworks.com and discuss the available options to solve this challenge.

Hi
thanks a lot because of this amazing add-on , it really helped me a lot , specially the formula column .
but here is a little problem ,
I create my structure and add "Start Date" and "End Date" column, start and end dates shown for Epics , Story and Tasks , but I cant see start and End date for Version and Project, But I really need it ,
please help me
best regards

Thanks for the kind words! Glad to know Formula column worked for you.

We'll be happy to assist you with any challenges you experience. The Start Date / Finish Date seems to be custom fields, which JIRA does not provide for Projects and Versions. Please write us to support@almworks.com and we'll be happy to discuss ways to approach this.

I am sorry that you had an unsatisfactory experience with our add-on and support. I can see from the support ticket that many people from our team were involved in solving this case. Unfortunately, it wasn't an easy one. But it also seemed that the problem was not necessarily located in Structure, and we were trying to get Atlassian involved in solving it.

JIRA server with multiple add-ons is a system with many moving parts. While we do our best to solve a problem regardless of the configuration, it sometimes involves other parties.

If you're willing to work with us a little more to try to restore Structure's functionality, we'll make another go at it, potentially with Atlassian support.

Structure is an indispensable add-on for my daily work. I use it for release and sprint planning, for planning the team capacities, work log reports,...., or just to get a quick overview over a new project. Structure gets the job done. I can't think of working with JIRA ever again without Structure.
Great tool + great support = great experience
Thank you,
Alain

After month of evaluating several plugins for better transparency, planning and collaboration we happily decided to use Structure. The main reason is that in contrast to similar plugins Structure remains very close to what a user already knows and applies in JIRA and how very little one needs to learn to use it to its full potential. Most importantly, there is zero need to adopt you processes to the tool, you can adopt the tool to your needs.
Saying that it is even more impressive how versatile and powerful Structure is without forcing you into new concepts or ways of working with JIRA. Be it temporary collaboration, long term milestone planning, calculations, testing, reporting, coordinating, tracking, grooming, sprint planning, editing issues, new hierarchies (using issue links), etc., all that and more can be easily realized.

This is an amazing piece of software. The responsiveness, speed, and interface is actually better than Jira's native interface. Compare loading thousands of issues in a single page vs 1000 on the standard issue navigator and you can see a huge difference.
It is an excellent replacement for the Jira issue navigator as it lets you quickly perform in-line editing which has been an outstanding feature request for the longest time. But I'm really short-changing it if all you're going to do is using it for issue navigating.
I've been testing it for generating roll-up reports with custom formulas, Gantt charting. This is like Excel + Jira. The fidelity of the Excel exports are also fantastic. There always seems to be something I discover each day that is a little more amazing.

David, that is so great to hear that Structure works for you so well. Thank you very much for your review! We'll do our best to continue expanding Structure's toolset. Feel free to reach out to support@almworks.com or to me personally if you have any feature suggestions.

Hi Jose, Structure just becomes read-only if its license becomes invalid. The users still have access to their data, but they cannot change structures. All Jira functionality remains untouched and fully working. It shouldn't present any problems, and we never had any reports about such cases.

I understand that your experience was different. I'm sorry about that. Did you create a support ticket? I can't find tickets in our support system based on your name. Our support team is always ready to help and if there is indeed a problem in the app, we'll have it addressed quickly or offer a workaround.

By the way, you can get additional evaluation licenses if you haven't enough time to try the product. Let me know at sereda@almworks.com if you need help with that.

Reviews for Data Center

Great tool. We are testing this for a month and would like to use it as our PPM tool. One concern about the progress, based on our testing ,all the columns are still configurable even we only assign view permission to people. Then in that way everyone will see different columns and different progress. Is there any way to lock down the columns and configurations?

Regarding the columns configuration, users can *adjust* what they are seeing, but they will not be able to overwrite the view shared with other people. You can tell that a view is adjusted by spotting a "*" symbol near the view name. You can also revert to the saved view. By design, there's no way to restrict users from adding more columns or changing column configuration.

Also, you can use Perspectives to get a URL that always opens in a predefined configuration.

Feel free to reach us at support@almworks.com and discuss the available options to solve this challenge.

Hi
thanks a lot because of this amazing add-on , it really helped me a lot , specially the formula column .
but here is a little problem ,
I create my structure and add "Start Date" and "End Date" column, start and end dates shown for Epics , Story and Tasks , but I cant see start and End date for Version and Project, But I really need it ,
please help me
best regards

Thanks for the kind words! Glad to know Formula column worked for you.

We'll be happy to assist you with any challenges you experience. The Start Date / Finish Date seems to be custom fields, which JIRA does not provide for Projects and Versions. Please write us to support@almworks.com and we'll be happy to discuss ways to approach this.

I am sorry that you had an unsatisfactory experience with our add-on and support. I can see from the support ticket that many people from our team were involved in solving this case. Unfortunately, it wasn't an easy one. But it also seemed that the problem was not necessarily located in Structure, and we were trying to get Atlassian involved in solving it.

JIRA server with multiple add-ons is a system with many moving parts. While we do our best to solve a problem regardless of the configuration, it sometimes involves other parties.

If you're willing to work with us a little more to try to restore Structure's functionality, we'll make another go at it, potentially with Atlassian support.

Structure is an indispensable add-on for my daily work. I use it for release and sprint planning, for planning the team capacities, work log reports,...., or just to get a quick overview over a new project. Structure gets the job done. I can't think of working with JIRA ever again without Structure.
Great tool + great support = great experience
Thank you,
Alain

Cloud Pricing

Server Pricing

Data Center Pricing

Pricing FAQ

How does server app pricing work?

Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

How do I determine my server pricing?

Apps are billed based on the number of users in your host product. For Jira Server 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (50 users) and Jira Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of Jira Server prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

Do you offer academic, community, or open-source licenses?

For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.

How can I buy apps for my legacy Jira Server or Confluence Server license?

If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

Purchase the app at the non-legacy Unlimited (10000+ users) tier.

Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.

Installation

Locate Structure for Jira - Projects at Scale via search. The appropriate app version appears in the search results.

Click Try free to begin a new trial or Buy now to purchase a license for Structure for Jira - Projects at Scale. You're prompted to log into MyAtlassian. Structure for Jira - Projects at Scale begins to download.