-
Suggestion
-
Resolution: Unresolved
-
37
-
28
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; however there are not currently any plans to implement this suggestion.
While we absolutely understand many the logic behind many of the requests for subcomponents, we strongly believe that our focus should be on making JIRA simpler and easier to use. Simply put, additional levels of hierarchy for components is likely to add complexity on a conceptual level, at a technical level (more bugs and slower performance) and will lead to a more confusing UI.
There are several add-ons available on the Marketplace addressing the requirements outlined below:
- Subcomponents for JIRA Cloud
- Component/Subcomponent/Bundle Versions (for JIRA Server)
- Subcomponents for JIRA (for JIRA Server)
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
Original request description:
As a person responsible for running the project I need to have the tools aligned with my projects' structures. My projects are organised in a large hierarchical groups of components. I need to be able to assign the JIRA issue to a whole group of components, as well as individually to any component within the system and be able to interact with issues in JIRA based on this assignment - i.e. all issues for component group, including both issues which are assigned to group as well as issues assigned to individual components within that group.
- causes
-
JSWCLOUD-5351 Option for Component View / Project Components to be pulled from a cascading select custom field.
- Closed
- is duplicated by
-
JRACLOUD-28502 Support for Sub Components
- Closed
-
JRACLOUD-34523 Need Subcomponents
- Closed
- is related to
-
JRACLOUD-4446 Sub-issues should be able to contain their own sub-issues
- Closed
-
JRASERVER-846 Support for subcomponents
- Closed
- relates to
-
JRACLOUD-3501 Allow Versions of components
- Gathering Interest
-
JRACLOUD-5721 Enhance 'Project Category' functionalty (versions/components/roadmap) and allow nested categories
- Gathering Interest