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

Component and Bundle Versions for JIRA

by The Starware, Inc. for JIRA Server 5.2 - 6.4.5
Supported
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

    (7)Sign in to write a review »
    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
    by wandisco_rich on 2014-01-08
    This plugin fills a massive gap but its lacking in some fundamentals. Deniz Oguz - is there a way to map the components to any version (free text?) instead of the versions within the project the issue is raised in? The chances of releasing components with the same version name as the project I'm working on is slim. Use case: we're building an application and pulling in a number of upstream components also used for other applications. Upstream-Component1 has its own release convention - its at version 10.8. Our latest application sprint is pulling in that component but the release of the application is only at 1.3. Due to the way the mapping is locked to the application versions, its not possible to create an issue against the 1.3 application release and force the user raising the issue to enter a component version which is actually relative to the component's release numbering. Can you make the component release version a free text field or associated it with another projects versions? That would be useful, right now this is pretty useless but close enough to being perfect for what we need that I'm posting this here :) --------------------------------------------------------------------------------------------------------------------------------------------------- To follow up on your response: I don't want to pollute my project with a long list of (component) release versions. If I've got 5 upstream components, all with their own release numbering, I'd have to populate the project versions list with near 100 version numbers. That makes raising issues cumbersome for the user who has to trawl through a long list of Released, Unreleased version numbers. That drop down would dominate the whole page making that option impractical. My component release numbers are in actual fact, already listed in the version of another project. Why can't I map those versions to my component instead and link them up? --------------------------------------------------------------------------------------------------------------------------------------------------- Next follow up: Until the option to enter free text or associate a component to another projects versions we will not be purchasing this. Best of luck!
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    Vendor response

    Hi wandisco_rich, You do not need to release your components with the same version name as the project. The plugin changes how to versions defined in "Project's Version Tab" behaves. The original version definitions of JIRA serves as a version repository, they are not project versions any more. First of all, define all possible component and project versions (your project versions and all versions of all components) within Project's Version administration tab. This is standard JIRA feature. Just entering version name should be enough, because release date and status may change for each component or bundle. After that, you need to define which of these versions are project (bundle) versions and which of them are component versions, this is done using two new tabs added by our plugin, just below the original Version tab: 1) Bundles Tab: Define which of versions are bundle/project versions and when they are released or to be released. If you do not select any component at issue screen only bundle/project versions are allowed in version fields. 2) Component Versions Tab: Define which components has which versions and when they are released or to be released. If a component is selected at issue screen, the plugin will only allow versions belonging to component to be selected. If we summarise the above statement, you do not need to release components with the same versions with you main project. Just define all possible versions at original project versions tab and map them to suitable components and bundles using our plugin. Do not hesitate to ask for further clarification please. Thanks for your feedback. ----------------------------------------------UPDATE---------------------------------- You are actually mapping components to versions defined in your project's version list. It is correct that you project version list will be longer than necessary. But it will not be visible to anyone other than you JIRA administrator. Even he will not use it anymore other than adding new versions to list. Everyone either raising issues or working on them will just see only mapped versions. I fish I could eliminate this also but versions are core feature of JIRA and a lot of other features are tied to it.
    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 James Barwick on 2014-08-23
    Doesn't fit my need. My needs are WAY more simplified than this plug-in. This plug-in assumes I am developing components with versions. What I need is simply a map between a component version field and the project version. Example: Project version 5.0 has component a version 2.46 and component b version 1.2. Project version 5.1 has component a version 2.47 and component b version 1.3. That's all. Simple. No fuss. On issue entry, if a person places an issue against project 5.0 component a, all the lists will show component a 2.46. If a person places n issue against project 5.1 component b, all the lists will show component a 2.47. Simple. The component may be under development by a different vendor, or my be a separate project.
    Was this review helpful?YesNo

    Vendor response

    Yes, plugin is designed for the use cases in which you want to limit versions available for each component separately, using the Jira's own version field(this fied is important because it has special usage in various places within jira). In addition to existing version field you want one more version field whose content will change depending on the projects version field. Is this what you are asking? Thanks for the feedback.

    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 original 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.
    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

    Support

    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.15 JIRA Server 5.2 - 6.4.5 Released 2015-04-07

    - Now enforcing component versions from issue creation of administrative screen.

    - More robust way to listen component change events

    Installation

    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