528
Customers have installed this app in at least 528 active instances.
528
Customers have installed this app in at least 528 active instances.
    by StarwareTop Vendor
    Starware is a Top Vendor.  Top Vendors have high standards for app quality, reliability, and support.

    Learn more

    for Jira Server 8.0.0 - 8.7.1, Jira Data Center 8.0.0 - 8.7.1 and more versions
    Versions available for Jira Server 5.2 - 7.13.12
    Unsupported
    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Supported
    Starware supports this app.

    Get support

    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Supported
    Starware supports this app.

    Get support

    Jira Service Desk
    This app 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

    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 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 component versions as bundles with specific version information. You can use provided JQLs to query issues of bundle, use bundle custom fields to display bundles of issues or use gadgets to enhance dashboards.

    Define Hierarchy of Components or Projects

    Component Specific Versions

    Group components as bundles with 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 component versions as bundles with specific version information. You can use provided JQLs to query issues of bundle, use bundle custom fields to display bundles of issues or use gadgets to enhance dashboards.

    More details

    This app has different builds for Jira 7 and Jira 8. Please navigate to versions tab for Jira 7.

    The plugin extends Jira's component and version management capability with component specific versions, subcomponents, version graphs and bundles and sub-projects.

    • REST API for every function
    • Define component specific versions and enforce these during issue operations.
    • Define subcomponents and virtual components for hierarchy of components
    • Define hierarchy of projects using sub-projects feature including virtual projects
    • Define version hierarchy for visualization and query
    • Workflow post functions, custom fields and dashboard widgets
    • Component release calendar
    • 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

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

    More details

    This app has different builds for Jira 7 and Jira 8. Please navigate to versions tab for Jira 7.

    The plugin extends Jira's component and version management capability with component specific versions, subcomponents, version graphs and bundles and sub-projects.

    • REST API for every function
    • Define component specific versions and enforce these during issue operations.
    • Define subcomponents and virtual components for hierarchy of components
    • Define hierarchy of projects using sub-projects feature including virtual projects
    • Define version hierarchy for visualization and query
    • Workflow post functions, custom fields and dashboard widgets
    • Component release calendar
    • 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

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

    Reviews for cloud

    (17)
    Sign in to write a review
    Working good but still need to exercise some features.
    Was this review helpful?YesNo
    Starware

    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 David Morgan 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.
    4 out of 4 found this review helpful
    Was this review helpful?YesNo
    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 5 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
    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

    Reviews for server

    (17)
    Sign in to write a review
    by Nataliia Lytvynenko on 2019-09-23
    Hi, I have just installed a trial version of plugin But I don't see button , near the project name, where I can select subproject. Could you please help me with it?
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    Starware

    Your administrator should enable subprojects for your project or globally from global add-on settings. Please ask your questions on our issue tracker, this place is not suitable for discusion.

    by testcf on 2019-07-03
    Very useful. Bug: The subcomponent disappeared sometime in JSD portal. Request for new feature: Components version support for JSD
    Was this review helpful?YesNo
    by Steven Behnke on 2019-05-15
    An excellent suite of features. We use the Component/Versions, subcomponents, and sub projects features in a large jira instance. The developer/support for this plugin is EXCELLENT! Fantastic experience! Thanks!
    Was this review helpful?YesNo
    by Rick van Twillert on 2018-06-04
    Besides the indispensable features this add-on provides for our business, the support is also truly amazing. There's always a solution provided/suggested within a few hours. Keep up the great job Deniz!
    Was this review helpful?YesNo
    by Gantner on 2018-02-22
    Support for this plugin is extremely fast. I had created an issue, and within an hour, I got a response, and developer promised to fix it in next release. The ticket is in resolved status by now, and I will check this after new version is released.
    Was this review helpful?YesNo

    Reviews for Data Center

    (17)
    Sign in to write a review
    Working good but still need to exercise some features.
    Was this review helpful?YesNo
    Starware

    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 David Morgan 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.
    4 out of 4 found this review helpful
    Was this review helpful?YesNo
    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 5 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
    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

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    10 users$1025 users$15050 users$280100 users$520250 users$950500 & upAdditional pricing details
    50 users$260/year100 users$480/year250 users$850/year500 users$1,200/year750 users$1,550/year1000 & upAdditional pricing details

    Pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 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 Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app 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?

    Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

    Can I install this app in a Data Center product?

    Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.

    Learn more about Data Center approved apps

    What type of license do I need if I'm using this app in a Data Center product?

    Because this app has a Data Center approved version, you should purchase a Data Center license for the app.

    If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.

    Learn more about Data Center licensing

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

    For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.

    Community and open-source licenses are available for server apps. Learn more about community and open source licenses.

    Can I extend my free trial?

    For server apps, you can extend your app 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 app listing in UPM from your Atlassian product, and you're all set.

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

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

    Learn more

    Pricing FAQ

    How does Data Center app pricing work?

    Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.

    If app 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 Data Center pricing?

    Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

    Can I install this app in a Data Center product?

    Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.

    Learn more about Data Center approved apps

    What type of license do I need if I'm using this app in a Data Center product?

    Because this app has a Data Center approved version, you should purchase a Data Center license for the app.

    If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.

    Learn more about Data Center licensing

    Do you offer academic, community, or open-source licenses for Data Center apps?

    For Data Center apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.

    Community and open-source licenses are not available for Data Center apps. Learn more about community and open source licenses.

    Can I extend my free trial?

    For Data Center apps, you can extend your app 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 app listing in UPM from your Atlassian product, and you're all set.

    Starware is a  Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.

    Starware is a  Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.

    Vendor support resources

    Documentation

    Find out how this app works.

    Community

    Community discussions connect you to the vendor and other customers who use this app.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

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

    Vendor support resources

    Documentation

    Find out how this app works.

    Community

    Community discussions connect you to the vendor and other customers who use this app.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

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

    Versions

    Version 1.14.0 Jira Server 8.0.0 - 8.7.1 Released 2019-12-23

    Summary

    Data Center compatibility.

    Details

    Any customer running this application on a DC Instance will need to convert their license over to a DC App license if they intend on upgrading to this version in the future.

    For more information see: https://www.atlassian.com/licensing/data-center-approved-apps#

    Please contact us before upgrading to this version if you are using this app on a DC instance. If your license start date is after September 3, 2019, you need to convert your license to a DC license.

    Versions

    Version 1.14.0 Jira Data Center 8.0.0 - 8.7.1 Released 2019-12-20

    Summary

    Data Center compatibility.

    Details

    Any customer running this application on a DC Instance will need to convert their license over to a DC App license if they intend on upgrading to this version in the future.

    For more information see: https://www.atlassian.com/licensing/data-center-approved-apps#

    Please contact us before upgrading to this version if you are using this app on a DC instance.

    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 apps or Find new add-ons from the left-hand side of the page.
    4. Locate Configuration Management Toolkit via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Configuration Management Toolkit. You're prompted to log into MyAtlassian. Configuration Management Toolkit 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 Configuration Management Toolkit versions compatible with your instance, you can look through our version history page.

    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 apps or Find new add-ons from the left-hand side of the page.
    4. Locate Configuration Management Toolkit via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Configuration Management Toolkit. You're prompted to log into MyAtlassian. Configuration Management Toolkit 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 Configuration Management Toolkit versions compatible with your instance, you can look through our version history page.

    Similar apps