-
Suggestion
-
Resolution: Won't Do
-
None
-
19
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi all,
Thanks for providing your thoughts and votes on this suggestion. I know it's been a while since we last commented on this suggestion and I am sorry to have kept you so long without a clear answer.
As Jira server team we have once again reviewed how this suggestion is aligned with our strategy and priorities. I am affraid we are not planning to invest in support for subcomponents.
While we absolutely understand 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.
Meanwhile, there are several add-ons available on the Marketplace addressing the requirements outlined below:
Since investing in support for subcomponents is not aligned with our strategy and roadmap, we will be closing this issue. I understand that our decision may be disappointing but we also hope you will appreciate our candid and transparent appraoch. Please don't hesitate to contact me if you have any questions.
Regards,
Gosia Kowalska
Senior Product Manager, Jira Server
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
-
JSWSERVER-5351 Option for Component View / Project Components to be pulled from a cascading select custom field.
- Closed
- is duplicated by
-
JRASERVER-3813 Add linking feature to components
- Closed
-
JRASERVER-13275 sub components
- Closed
-
JRASERVER-28502 Support for Sub Components
- Closed
-
JRASERVER-34523 Need Subcomponents
- Closed
- is incorporated by
-
JRASERVER-12241 Support for Product Suites / Sub-Projects
- Closed
- is related to
-
JRASERVER-1538 Filter on Versions and Components across Projects
- Closed
-
JRASERVER-2047 Hierarachical versioned components, with cross-referencing
- Closed
-
JRASERVER-4446 Sub-issues should be able to contain their own sub-issues
- Closed
-
JRASERVER-11125 JIRA 4.0 Enterprise Requirements
- Closed
-
JRASERVER-12241 Support for Product Suites / Sub-Projects
- Closed
-
JRASERVER-24962 Enable View permissions for components
- Closed
- relates to
-
JRASERVER-3501 Allow Versions of components
- Closed
-
JRACLOUD-846 Support for subcomponents
- Gathering Interest
-
JRASERVER-5721 Enhance 'Project Category' functionalty (versions/components/roadmap) and allow nested categories
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...