Customers have installed this add-on in at least 40 active instances.
    by Broken Buildfor JIRA Server 7.0.0 - 7.2.3 and more versions
    Versions available for JIRA Server 5.0.1 - 6.4.14
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Broken Build supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    Organize your projects better with versions hierarchy, versions field picker and subversions() JQL function

    Organize your projects better with versions hierarchy, versions field picker and subversions() JQL function

    Versions Hierarchy

    Versions Field Picker

    Browse and search issues

    Visualize complex multi-package and multi-module project releases by versions hierarchy

    Edit issue fixVersion field with new versions field picker right on the create/edit issue screen

    Browse issues for version hierarchy and search using new JQL subversions() function

    More details

    With just few clicks you can convert a plain list of JIRA project versions into hierarchical tree to visualize complex project releases consisted of multiple releases of different modules.

    • Create and modify project versions hierarchy with drag & drop UI
    • Edit issue's fixVersions and affectVersions fields with new Versions Field Picker
    • Find versions in large hierarchy using filtering by name
    • Browse issues of particular version and all it's nested versions
    • Search issues in versions hierarchy using subversions() JQL function
    • Filter versions by "release" and "archive" status when creating versions hierarchy
    • Multi-select drag&drop versions to design a hierarchy

    User reviews

    Sign in to write a review »
    by Nicolas Couronne on 2016-07-27
    Interresting add-on, but why a issue found and fix in under nest versions is visible in the upper-nest version of the tree ? A bug ? I would an extension where a found in version bug is automatically propagated to under nest version if issue is not fix. What do you think ?
    Was this review helpful?YesNo
    by Fabio Genovese on 2016-05-09
    This is very important Addon. I mean: as a developer, my opinion, have a hierarchy of version means have all information ordered. I'm looking forward to have addon available in my cloud instance. :-)
    Was this review helpful?YesNo


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons 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 add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on 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 tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications 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 add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

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

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on 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 add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons 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 add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more


    Broken Build supports Versions Hierarchy. You can visit the support site to get help.

    Get support


    Version 1.5.0.jira7 JIRA Server 7.0.0 - 7.2.3 Released 2016-10-07


    Enable versions hierarchy picker for "Affects Version(s)" field


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Versions Hierarchy via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Versions Hierarchy. You're prompted to log into MyAtlassian. Versions Hierarchy begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older Versions Hierarchy versions compatible with your instance, you can look through our version history page.

    Similar add-ons