Extend projects with Subcomponents, Component Versions, Packages, Component and Version custom properties
Extend projects with Subcomponents, Component Versions, Packages, Component and Version custom properties
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
Sandbox Jira | Documentation | Support
Subcomponents app implements the following missing parts of Jira projects functionality:
- Subcomponents - extend components with subcomponents hierarchy
- Component versions - link versions to components to make them releasable
- Packages - group system versions into a product release
- Component properties - add more details to components + componentProps() JQL search
- Version properties - add more details to versions + versionProps() JQL search
- Global settings - enable extensions for projects types
- Custom permissions - delegate manage extensions to non-project admin users
- Public REST API - create integrations, pull and post data from/to extensions
More details
Sandbox Jira | Documentation | Support
Subcomponents app implements the following missing parts of Jira projects functionality:
- Subcomponents - extend components with subcomponents hierarchy
- Component versions - link versions to components to make them releasable
- Packages - group system versions into a product release
- Component properties - add more details to components + componentProps() JQL search
- Version properties - add more details to versions + versionProps() JQL search
- Global settings - enable extensions for projects types
- Custom permissions - delegate manage extensions to non-project admin users
- Public REST API - create integrations, pull and post data from/to extensions
Reviews for cloud
(22)Sign in to write a review
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
Hi Vishal,
Thank you for your feedback! We will investigate how your suggestions can be implemented.
Regards,
Vasiliy Krokha [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
Reviews for server
(22)Sign in to write a review
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:
- https://developer.atlassian.com - how to create it
- https://community.developer.atlassian.com - if something doesn't work
Again, thanks for our feedback and good luck!
Regards,
Vasiliy
Reviews for Data Center
(22)Sign in to write a reviewHi 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
Hi Vishal,
Thank you for your feedback! We will investigate how your suggestions can be implemented.
Regards,
Vasiliy Krokha [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
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$10 | 25 users$100 | 50 users$200 | 100 users$400 | 250 users$800 | 500 & upAdditional pricing details |
| 50 users$200/year | 100 users$400/year | 250 users$800/year | 500 users$1,200/year | 750 users$1,500/year | 1000 & 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 Management (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 Management, 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.
- 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.
- 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.
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 Management (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 Management, 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.
- 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.
- 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 provides support for this app.
Broken Build provides support for this app.
Vendor support resources
Find out how this app works.
Vendor support resources
Find out how this app works.
Versions
Version 3.3.17 • Jira Server 7.2.0 - 8.16.0 • Released 2021-04-13
Summary
Bug fixes
Details
Fixed:
- user without "manage subcomponents" permission can modify the hierarchy
Versions
Version 3.3.18 • Jira Data Center 7.2.0 - 8.16.0 • Released 2021-04-16
Summary
Fix for subcomponents picker not displayed in transition custom screen
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Subcomponents for Jira via search. The appropriate app version appears in the search results.
- 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.
- Enter your information and click Generate license when redirected to MyAtlassian.
- 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.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Subcomponents for Jira via search. The appropriate app version appears in the search results.
- 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.
- Enter your information and click Generate license when redirected to MyAtlassian.
- 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
