20
436
Customers have installed this app in at least 436 active instances.
436
Customers have installed this app in at least 436 active instances.

    Subcomponents for Jira

    by Broken BuildTop Vendor
    Broken Build is a Top Vendor.  Top Vendors have high standards for app quality, reliability, and support.

    Learn more

    for Jira Server 7.2.0 - 8.4.1, Jira Data Center 7.2.0 - 8.4.1 and more versions
    Versions available for Jira Server 5.0.1 - 7.1.10
    Unsupported
    This app isn't formally supported.

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

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

    Get support

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

    Get support

    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Try it freeBuy it now

    Extend projects with useful component and version tools: Subcomponents, Component Versions, Packages and more

    Extend projects with useful component and version tools: Subcomponents, Component Versions, Packages and more

    Extend projects with useful component and version tools: Subcomponents, Component Versions, Packages and more

    Split and rule a project with Subcomponents

    Release components independently with Versions

    Group versions into Packages

    Convert project components into a meaningful hierarchy.

    Enable users to select components from the hierarchy in issues including Customer Portal.

    Find issues and create reports based on subcomponents hierarchy.

    Organize and manage release roadmap on a component level.

    Different teams can develop and release different components in one project.

    Filter and group versions by issue components when editing any issue Version fields.

    Organize and track multiple versions as a single product release

    Find all packages where an issue is implemented using Packages issue panel

    Search issues and create reports based on packages with packageVersions() JQL

    Split and rule a project with Subcomponents

    Release components independently with Versions

    Group versions into Packages

    Convert project components into a meaningful hierarchy.

    Enable users to select components from the hierarchy in issues including Customer Portal.

    Find issues and create reports based on subcomponents hierarchy.

    Organize and manage release roadmap on a component level.

    Different teams can develop and release different components in one project.

    Filter and group versions by issue components when editing any issue Version fields.

    Organize and track multiple versions as a single product release

    Find all packages where an issue is implemented using Packages issue panel

    Search issues and create reports based on packages with packageVersions() JQL

    More details

    Subcomponents app provides several project extensions which implement missing parts of Jira project functionality and enable you to work with Components and Versions more efficiently.

    Public demo Jira to check the latest Subcomponents version without installing it.

    Extensions and key features:

    • Subcomponents - extend components with subcomponents hierarchy
    • Component versions - link versions to components to make them releasable
    • Packages - group system versions into product release
    • Global settings - enable extensions for projects types
    • Custom permissions - delegate manage extensions to non-project admin users
    • Custom JQL functions - search issues and create reports based on extensions data
    • Public REST API - create integrations, pull and post data from/to extensions

    We are here to help you get started and use Subcomponents app:

    More details

    Subcomponents app provides several project extensions which implement missing parts of Jira project functionality and enable you to work with Components and Versions more efficiently.

    Public demo Jira to check the latest Subcomponents version without installing it.

    Extensions and key features:

    • Subcomponents - extend components with subcomponents hierarchy
    • Component versions - link versions to components to make them releasable
    • Packages - group system versions into product release
    • Global settings - enable extensions for projects types
    • Custom permissions - delegate manage extensions to non-project admin users
    • Custom JQL functions - search issues and create reports based on extensions data
    • Public REST API - create integrations, pull and post data from/to extensions

    We are here to help you get started and use Subcomponents app:

    Reviews for cloud

    (20)
    Sign in to write a review
    by Mirco Stange on 2017-08-16
    Quite a good addon. However, it seems to have dramatically increased in price for the starter edition. When first licensed May 2015, it was $10. The next renewals May 2016 and 2017 were $25 each. Now the price seems to be $50. That is a 500% price increase! For what it delivers, this seems overpriced now. There is another plugin that delivers similar funcationality. Perhaps I have to look at that one...
    10 out of 10 found this review helpful
    Was this review helpful?YesNo
    by Fabio Genovese on 2016-05-09
    Very good addon. Useful, extend native JIRA functionality adding with a good feature: hierarchy for components. This is a very good way to organize all.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo
    by David Morgan on 2016-02-08
    This add-on works with JIRA native functionality for Components and Versions. It essentially allows: (A) a 1-to-many relationship (enforced constraint) between JIRA Components and JIRA versions and; (B) a hierarchical relationship for JIRA Components in order organise them better (useful if you have a lot). Positives: 1. Intuitive UI 2. Good documentation 3. Goes someway to filling the void caused by JIRA's lack of native functionality for component versioning 4. Because it works with JIRA native Components and Versions it can be removed without losing your key data. In other words, it is safe to uninstall in the future (like when JIRA address this natively in 2099 :) as you just lose relationships introduced by this add-on as opposed to the Components and Versions themselves. Negatives: 1. For the JIRA "Fix Version/s" field, user has to click the "version picker" button (this is a button this add-on plugs into the JIRA UI) in order for the constraint between Component and Version to be enforced. The developer can bypass this and select any fix version in the native JIRA field if they so desire. This is a MAJOR limitation because it means you are dependent on the user (not the software) to ensure the correct fix versions are assigned to a JIRA issue. 2. It does not support Virtual Components for creating a component hierarchy (you would use this to better organising your components). In our case, we have 15 Windows Services that are each JIRA Components but we group them under the category "Windows Services" so they appear in a hierarchical format when the user selects the "version picker" button (which is plugged into the JIRA UI by this add-on). The problem is that "Windows Services" itself is not a real software component but still you must add it as one in order to represent the hierarchy. The problem is that a user can then erroneously assign issues to this virtual component. 3. Bug. On the JIRA Edit page (click "Edit" button on a JIRA issue) if you change the "Component" and then click the "version picker" button for "Fix Version/s", it does not pick up the change you made in the Component field until you save the issue first. This is a real nuisance as you have to save and then reopen the issue. I'm sure this can be fixed relatively easily so I hope the developer addresses it soon. 4. Requires JIRA Project Admin permissions in order to add new versions and set the relationships between components and versions. To be fair, this is probably an inherited limitation from JIRA itself so not sure that much can be done here. The competing component called "Component/Subcomponent/Bundle Versions" is more functionally rich and significantly cheaper but the UI is not at all intuitive so we opted to purchase this component despite the negatives I mention above. Still, it was a borderline decision and we did so in the hope that the developer addresses some of the limitations I mention here in a future version. Good but more work needed.
    3 out of 3 found this review helpful
    Was this review helpful?YesNo
    Broken Build

    Hi David,

    Thanks for your review and feedback!

    #1, #2 are in our roadmap, #3 fixed in v1.6.2, #4 works as designed

    Vasiliy Krokha

    Broken Build

    by Vishal Singh on 2016-01-07
    Overall very good plugin to track releases at component version level. But off and on we are receiving feedback from various teams that if some constraint or workflow can be created around component version release then it will be very helpful. What I mean by constraints: 1. No new issues can be added to a released component version 2. Component version can not be released if any of the related issues is still in open state (i.e. not in [Closed, Resolved] state).
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Broken Build

    Hi Vishal,

    Thank you for your feedback! We will investigate how your suggestions can be implemented.

    Regards,

    Vasiliy Krokha [Broken Build]

    by Guenter Frick on 2015-06-20
    Uses the same table structure to deploy the "sub-components". So it's not a real component to subcomponent relation. When opening the list of components ALL subcomponents are listed as well. In this setup the plugin is not usable. Guenter
    1 out of 2 found this review helpful
    Was this review helpful?YesNo
    Broken Build

    Hi Guenter,

    The relation between component and subcomponent is in fact real, but your concern is about that sub-components shouldn't be displayed in components list. This means that from your point of view sub-components are not really a components, but something else which may also be true. In our implementation we treat subcomponent as a component which is put at some level of components hierarchy, but essentially components and subcomponents are same entities. That is why they are all shown in project component list.

    Regards,

    Vasiliy

    Read more reviews

    Reviews for server

    (20)
    Sign in to write a review
    by Piotr Mińkowski on 2018-02-20
    Following your documentation: "Project version names should be unique within one project. That's why real version name if duplicated is automatically prefixed with component ID which it is linked to.". In my opinion it's not automatically prefixed with component ID. If I create new version of component, for example 1.1, the version with that name is created without any prefix. Then if I would like to create the same version for another component, it's not permited due to version name conflict.
    Was this review helpful?YesNo
    Broken Build

    Hello Piotr,

    You are right, the documentation needs to be fixed and now it's done. We have also described changes for version naming in the release notes blog post.

    Thanks for your feedback!

    Regards,

    Vasiliy

    by Evgeny Erofeev on 2017-11-23
    too high price for quite modest, doubtful functionality
    2 out of 3 found this review helpful
    Was this review helpful?YesNo
    Broken Build

    Hi Evgeny,

    Thanks for your feedback here and while uninstalling the app, we've got both.

    Since there are millions of different use cases where Jira is used it is absolutely possible that for a small app which solves a particular need or adds a small feature the price/value ratio is questionable. The key thing here is value, not the price. In 100% cases when clients said price is too high and we offered a significant discount - you know what happens... nothing. That simply means that the feature introduced by app itself doesn't bring any value to a particular customer and that's absolutely fine. Therefore I wouldn't agree with 'modest, doubtful functionality' term.

    That's I can recommend you a couple of resources for cost effective and 100% matching your needs solutions:

    Again, thanks for our feedback and good luck!

    Regards,

    Vasiliy

    by Mirco Stange on 2017-08-16
    Quite a good addon. However, it seems to have dramatically increased in price for the starter edition. When first licensed May 2015, it was $10. The next renewals May 2016 and 2017 were $25 each. Now the price seems to be $50. That is a 500% price increase! For what it delivers, this seems overpriced now. There is another plugin that delivers similar funcationality. Perhaps I have to look at that one...
    10 out of 10 found this review helpful
    Was this review helpful?YesNo
    by Fabio Genovese on 2016-05-09
    Very good addon. Useful, extend native JIRA functionality adding with a good feature: hierarchy for components. This is a very good way to organize all.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo
    by David Morgan on 2016-02-08
    This add-on works with JIRA native functionality for Components and Versions. It essentially allows: (A) a 1-to-many relationship (enforced constraint) between JIRA Components and JIRA versions and; (B) a hierarchical relationship for JIRA Components in order organise them better (useful if you have a lot). Positives: 1. Intuitive UI 2. Good documentation 3. Goes someway to filling the void caused by JIRA's lack of native functionality for component versioning 4. Because it works with JIRA native Components and Versions it can be removed without losing your key data. In other words, it is safe to uninstall in the future (like when JIRA address this natively in 2099 :) as you just lose relationships introduced by this add-on as opposed to the Components and Versions themselves. Negatives: 1. For the JIRA "Fix Version/s" field, user has to click the "version picker" button (this is a button this add-on plugs into the JIRA UI) in order for the constraint between Component and Version to be enforced. The developer can bypass this and select any fix version in the native JIRA field if they so desire. This is a MAJOR limitation because it means you are dependent on the user (not the software) to ensure the correct fix versions are assigned to a JIRA issue. 2. It does not support Virtual Components for creating a component hierarchy (you would use this to better organising your components). In our case, we have 15 Windows Services that are each JIRA Components but we group them under the category "Windows Services" so they appear in a hierarchical format when the user selects the "version picker" button (which is plugged into the JIRA UI by this add-on). The problem is that "Windows Services" itself is not a real software component but still you must add it as one in order to represent the hierarchy. The problem is that a user can then erroneously assign issues to this virtual component. 3. Bug. On the JIRA Edit page (click "Edit" button on a JIRA issue) if you change the "Component" and then click the "version picker" button for "Fix Version/s", it does not pick up the change you made in the Component field until you save the issue first. This is a real nuisance as you have to save and then reopen the issue. I'm sure this can be fixed relatively easily so I hope the developer addresses it soon. 4. Requires JIRA Project Admin permissions in order to add new versions and set the relationships between components and versions. To be fair, this is probably an inherited limitation from JIRA itself so not sure that much can be done here. The competing component called "Component/Subcomponent/Bundle Versions" is more functionally rich and significantly cheaper but the UI is not at all intuitive so we opted to purchase this component despite the negatives I mention above. Still, it was a borderline decision and we did so in the hope that the developer addresses some of the limitations I mention here in a future version. Good but more work needed.
    3 out of 3 found this review helpful
    Was this review helpful?YesNo
    Broken Build

    Hi David,

    Thanks for your review and feedback!

    #1, #2 are in our roadmap, #3 fixed in v1.6.2, #4 works as designed

    Vasiliy Krokha

    Broken Build

    Read more reviews

    Reviews for Data Center

    (20)
    Sign in to write a review
    by Mirco Stange on 2017-08-16
    Quite a good addon. However, it seems to have dramatically increased in price for the starter edition. When first licensed May 2015, it was $10. The next renewals May 2016 and 2017 were $25 each. Now the price seems to be $50. That is a 500% price increase! For what it delivers, this seems overpriced now. There is another plugin that delivers similar funcationality. Perhaps I have to look at that one...
    10 out of 10 found this review helpful
    Was this review helpful?YesNo
    by Fabio Genovese on 2016-05-09
    Very good addon. Useful, extend native JIRA functionality adding with a good feature: hierarchy for components. This is a very good way to organize all.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo
    by David Morgan on 2016-02-08
    This add-on works with JIRA native functionality for Components and Versions. It essentially allows: (A) a 1-to-many relationship (enforced constraint) between JIRA Components and JIRA versions and; (B) a hierarchical relationship for JIRA Components in order organise them better (useful if you have a lot). Positives: 1. Intuitive UI 2. Good documentation 3. Goes someway to filling the void caused by JIRA's lack of native functionality for component versioning 4. Because it works with JIRA native Components and Versions it can be removed without losing your key data. In other words, it is safe to uninstall in the future (like when JIRA address this natively in 2099 :) as you just lose relationships introduced by this add-on as opposed to the Components and Versions themselves. Negatives: 1. For the JIRA "Fix Version/s" field, user has to click the "version picker" button (this is a button this add-on plugs into the JIRA UI) in order for the constraint between Component and Version to be enforced. The developer can bypass this and select any fix version in the native JIRA field if they so desire. This is a MAJOR limitation because it means you are dependent on the user (not the software) to ensure the correct fix versions are assigned to a JIRA issue. 2. It does not support Virtual Components for creating a component hierarchy (you would use this to better organising your components). In our case, we have 15 Windows Services that are each JIRA Components but we group them under the category "Windows Services" so they appear in a hierarchical format when the user selects the "version picker" button (which is plugged into the JIRA UI by this add-on). The problem is that "Windows Services" itself is not a real software component but still you must add it as one in order to represent the hierarchy. The problem is that a user can then erroneously assign issues to this virtual component. 3. Bug. On the JIRA Edit page (click "Edit" button on a JIRA issue) if you change the "Component" and then click the "version picker" button for "Fix Version/s", it does not pick up the change you made in the Component field until you save the issue first. This is a real nuisance as you have to save and then reopen the issue. I'm sure this can be fixed relatively easily so I hope the developer addresses it soon. 4. Requires JIRA Project Admin permissions in order to add new versions and set the relationships between components and versions. To be fair, this is probably an inherited limitation from JIRA itself so not sure that much can be done here. The competing component called "Component/Subcomponent/Bundle Versions" is more functionally rich and significantly cheaper but the UI is not at all intuitive so we opted to purchase this component despite the negatives I mention above. Still, it was a borderline decision and we did so in the hope that the developer addresses some of the limitations I mention here in a future version. Good but more work needed.
    3 out of 3 found this review helpful
    Was this review helpful?YesNo
    Broken Build

    Hi David,

    Thanks for your review and feedback!

    #1, #2 are in our roadmap, #3 fixed in v1.6.2, #4 works as designed

    Vasiliy Krokha

    Broken Build

    by Vishal Singh on 2016-01-07
    Overall very good plugin to track releases at component version level. But off and on we are receiving feedback from various teams that if some constraint or workflow can be created around component version release then it will be very helpful. What I mean by constraints: 1. No new issues can be added to a released component version 2. Component version can not be released if any of the related issues is still in open state (i.e. not in [Closed, Resolved] state).
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Broken Build

    Hi Vishal,

    Thank you for your feedback! We will investigate how your suggestions can be implemented.

    Regards,

    Vasiliy Krokha [Broken Build]

    by Guenter Frick on 2015-06-20
    Uses the same table structure to deploy the "sub-components". So it's not a real component to subcomponent relation. When opening the list of components ALL subcomponents are listed as well. In this setup the plugin is not usable. Guenter
    1 out of 2 found this review helpful
    Was this review helpful?YesNo
    Broken Build

    Hi Guenter,

    The relation between component and subcomponent is in fact real, but your concern is about that sub-components shouldn't be displayed in components list. This means that from your point of view sub-components are not really a components, but something else which may also be true. In our implementation we treat subcomponent as a component which is put at some level of components hierarchy, but essentially components and subcomponents are same entities. That is why they are all shown in project component list.

    Regards,

    Vasiliy

    Read more reviews

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    10 users$5025 users$11650 users$216100 users$396250 users$796500 & upAdditional pricing details
    50 users$600/year100 users$900/year250 users$1,300/year500 users$1,800/year750 users$2,300/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.

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

    Broken Build 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.

    Vendor support resources

    Documentation

    Find out how this app works.

    Versions

    Version 3.0.7 • Jira Server 7.2.0 - 8.4.1 • Released 2019-09-06

    Summary

    Fix subcomponents import model in built-in REST API docs

    Versions

    Version 3.0.7 • Jira Data Center 7.2.0 - 8.4.1 • Released 2019-09-06

    Summary

    Fix subcomponents import model in built-in REST API docs

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

    Similar apps