Customers have installed this add-on in at least 207 active instances.
    by The Starware for JIRA Server 7.0.0 - 7.1.7 and more versions
    Versions available for JIRA Server 5.2 - 6.4.13
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Atlassian Verified
    The Starware is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    The Starware supports this add-on.

    Get support

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

    Enables subcomponents, component specific versions and grouping of components as Bundles

    Enables subcomponents, component specific versions and grouping of components as Bundles

    Define Hierarchy of Components

    Force correct version selection based on component

    Group components as bundles with different version

    Create a component tree of project either using normal JIRA components or virtual components. On issue screens you can select components from the tree or as usual. Component specific versions are also supported.

    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

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

    • Define component specific versions and enforce these during issue operations.
    • Define subcomponents and virtual components
    • Highlight invalid versions (if exist) in issue detail page.
    • Component specific release date, description and released status.
    • Component release date calendar and widgets.
    • Define how to handle versions for multiple component selection
    • One click access to fixed or found issues for every component release and JQL functions for creating your own queries
    • JQL query to find out all invalid mappings (if exist)
    • Define bundles with a name and version and add different version of different components to this bundle.
    • Query issues at bundle level with provided JQL functions.
    • Issue release date custom field. Search & sort issues based on their release date.
    • Locales DE,TR,ES,FR,IT

    Please refer to Plugin's Help Page for details.

    User reviews

    Sign in to write a review »
    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.
    Was this review helpful?YesNo

    The Starware

    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 2 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

    The Starware

    Thanks a lot.

    by belkis genc on 2014-11-17
    Version control is an important part of making SW Development team work effectively , and version control practices help developers, and Configuration Management people manage the various components which are placed in a System. Currently, we are using Comp.Version Mapping plug in and our team members can easily see the current stable component version. They initiate and fix the issues by using this information quickly. Otherwise, it was difficult to find out that which component belongs to which version. This plug in provides a checkpointing of comp.versions.It is such well defined and designed , thanks to Rock Star Developer.
    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


    The Starware is Atlassian Verified. Verified add-on vendors demonstrate high quality, reliability, and business traction. Learn more

    Deniz Oguz supports Component/Subcomponent/Bundle Versions. You can visit the support site to get help.

    Get support


    Version 1.5.12-jira7 JIRA Server 7.0.0 - 7.1.7 Released 2016-05-25


    Minor bug fixes.


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

    Similar add-ons