Customers have installed this add-on in at least 116 active instances.

Component and Bundle Versions for JIRA

by The Starware, Inc. for JIRA Server 5.2 - 6.4.11
The Starware, Inc. supports this add-on.

Get support

    Enables grouping of Components as Bundles and allows component and bundle specific version numbers for issues

    Define component specific versions

    Force correct version selection based on component

    Group components as bundles with different version

    Define which versions are applicable for which components by mapping components to versions with component specific version release date and release status. Map multiple versions to multiple components at once.

    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

    Pricing overview

    Pricing details are loading…

    This add-on is not available for Cloud.

    You can browse available Cloud add-ons here.

    User reviews

    Sign in to write a review »
    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

    Vendor response

    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
    by Hilal Sener on 2014-11-16
    It did work well for me... This plugin allows you to easily choose the correct component version for your issue. It lists only versions of the component you select, not all project versions. Without this plugin, it is really hard to find the correct component version among hundreds of project versions. Great job Deniz Oguz.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    More details

    Component specific versions and grouping components are two of the most requested features of JIRA, JRA-3501, JRA-2744, JRA-3228, JRA-18987, JRA-846, JRA-34523, JRA-12241.This plugin enables you to:

    • Define component specific versions and enforce these during issue operations.
    • Highlight invalid versions (if exist) in issue detail page.
    • Component specific release date and released status.
    • Component release date calendar, with fixed issues
    • Define how versions are sorted
    • 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.

    Please refer to Plugin's Help Page for details.

    Paid-via-Atlassian pricing FAQ

    How does add-on pricing work?

    Just like your Atlassian host application, there are two pricing models for add-ons. Pick the model that matches your Atlassian product, and the same rules apply:

    Server pricing

    • Products and add-ons are hosted on your servers.
    • Licenses last forever and 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).

    Cloud pricing

    • Products and add-ons are hosted by Atlassian.
    • You are eligible for support and automatic version updates as long as your subscription is active.
    • Your subscription automatically renews every month. Annual pricing is also available.
    • Your pricing tier for host products and add-ons is automatically upgraded (as necessary) when you add users to your instance.

    Price changes

    • 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 pricing tier?

    Choose the same user tier you pay for in the Atlassian host application. For example, if you have a JIRA Server license for 25 users, you should purchase this tier. Even if fewer users want to use the add-on than your host application license, the two licenses should match exactly.

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

    Add-on purchase and renewal is half-price if you have an academic license for your Atlassian host application.

    Add-ons are always free for community and open-source licenses.

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

    Can I extend my free trial?

    You can extend your Server 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 Free Trial and you'll be directed to generate a license at MyAtlassian. Paste this license key into the add-on listing in UPM from your Atlassian host application, and you're all set.

    You cannot extend your Cloud free evaluation period. All Cloud add-ons are immediately subscribed by a user, and we provide a free evaluation of period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the add-on.

    How can I buy add-ons for my legacy JIRA or Confluence license?

    If you own a legacy JIRA Unlimited (100+ users) or Confluence 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, Inc. supports Component and Bundle Versions for JIRA. You can visit the support site to get help.

    Get support

    Release notes

    Version 1.4.16 JIRA Server 5.2 - 6.4.11 Released 2015-06-08


    Support for custom version fields (like Firmware Version etc) and PostgreSQL fix


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

    Similar add-ons