Customers have installed this add-on in at least 336 active instances.
    by StarwareAtlassian Verified
    Starware is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for JIRA Server 7.0.0 - 7.3.6 and more versions
    Versions available for JIRA Server 5.2 - 6.4.14
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    JIRA Service Desk
    This add-on is compatible with JIRA Service Desk.
    Starware supports this add-on.

    Get support

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

    Enables subprojects, subcomponents, bundles, component specific versions with complete REST API Support

    Enables subprojects, subcomponents, bundles, component specific versions with complete REST API Support

    Define Hierarchy of Components or Projects

    Component Specific Versions

    Group components as bundles with different version

    You can create component hierarchy for projects using normal JIRA components or virtual components to enable subcomponents. You can also create project hierarchy to enable subprojects using real or virtual projects.

    Force correct version(s) to be selected depending on the component selection in; issue create, edit, inline edit, workflow screens. Multiple component selection is also supported and unrelated versions are filtered out.

    Group different version of different components as bundles with a bundle specific version information.When no component is selected only bundle versions could be used.JQL functions to query issues of bundle are available

    More details

    For Jira 6, please use 1.7.7-jira6 version by clicking more versions link on the header.

    The plugin extends JIRA's component and version management capability with component specific versions, subcomponents, version graphs and bundles.

    • REST API for every function
    • Define component specific versions and enforce these during issue operations.
    • Define subcomponents and virtual components for grouping of components and issue query
    • Define subprojects
    • Define version graphs for visualization and query
    • Highlight/prohibit invalid versions everywhere
    • Workflow post functions
    • Component release date calendar and widgets
    • JQLs for version graphs, bundle, subproject, subcomponent and component versions
    • Define bundles and add different version of different components to this bundle for higher level release management
    • Issue release date custom field
    • Locales EN,DE,TR,ES,FR,IT

    Please refer to Plugin's Help Page for details. If you desired feature is not covered, please just ask on our support site.

    User reviews

    Sign in to write a review
    by Heidi Kiser on 2016-11-18
    Working good but still need to exercise some features.
    Was this review helpful?YesNo

    Thanks for the feedback. You can always submit feature requests and improvements on our issue tracker. We are currently working on new version. We will polish some features and add a few new ones.

    by DavidM on 2016-02-08
    This component is functionally rich (more so than competing components) but the usability experience needs some improvements. For example, the relationship/constraint between component and versions is not presented as intuitively as it could be. Also, the documentation is somewhat out-of-date with the software (e.g. "Component to Version Mapping" no longer exist in the latest software with that title). On the positives, I do like the Virtual Components feature to allow a hierarchical relationship of JIRA Components in order to organise them better. Also, it works with JIRA native Components and Versions so it can be uninstalled in the future without losing your key data. It is also well priced. Good but more work needed on the UI and documentation.
    3 out of 3 found this review helpful
    Was this review helpful?YesNo

    We have rewritten our documentation and moved to Confluence. We have also very detailed REST API documentation both on our Confluence page and on Apiary. We are also improving our UI, we have recently added ability to create component and versions without navigating to JIRA's own component and version page recently. We are working on other features too. Thanks for your feedback.

    by Aykut KANYILMAZ on 2015-08-05
    0 out of 4 found this review helpful
    Was this review helpful?YesNo
    by Jinbo Su on 2015-06-10
    This plugin is very helpful if you have different versions for components and sometimes you also need to group some specific versions of multiple components together (into one “bundle”). All settings can be easily configured through the “Add-ons” page so users can define customized behaviors for the version fields (now the plugin supports custom version fields as well). I am also very glad that the plugin has powerful APIs so automation for release or versioning process could be possible. The developer provided great support and quick resolution when we requested a new feature :-)
    Was this review helpful?YesNo

    Thanks a lot.


    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.

    Note: While this add-on has features specific to JIRA Service Desk, the add-on 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 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

    Starware is an vendor, committed to providing support for their add-ons at least 8 hours a day, 5 days a week.

    Vendor support resources


    Find out how this add-on works.


    Community discussions connect you to the vendor and other customers who use this add-on.

    Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this add-on.


    Version 1.7.7-jira7 JIRA Server 7.0.0 - 7.3.6 Released 2017-04-12


    Fixed no version displayed when a component is not selected problem


    Please check release notes for more details.


    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 Component/Subcomponent/Bundle Version 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 Component/Subcomponent/Bundle Version. You're prompted to log into MyAtlassian. Component/Subcomponent/Bundle Version 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 Component/Subcomponent/Bundle Version versions compatible with your instance, you can look through our version history page.

    Similar add-ons