Details

    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update – 31 December 2015

      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:

      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.

        Attachments

        1. classic_board_component.png
          6 kB
          Stefan Egli
        2. subcomponets-field-picker.png
          24 kB
          Vasiliy Krokha [Broken Build]

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                meenu Meenu Gaba
              • Votes:
                915 Vote for this issue
                Watchers:
                472 Start watching this issue

                Dates

                • Created:
                  Updated: