Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-25467

Ability to have different Issue Type hierarchy to associate with different project.

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Currently, we support only one issue type hierarchy. As a JIRA Admin of a large JIRA site, my Organization has multiple teams in them and every has a different requirement on how they see Issue type hierarchy.

      Suggestion:

      First.

      It would be better to have multiple "Issue Type Hierarchy" to be configured on a site which can be associated with different project.

      • Issue Type hierarchy A can be associated with project A1, A2 and A3
      • Issue Type hierarchy B can be associated with project B1, B2 and B3 and so on.

      Second.
      With this change, it would be also helpful if the below could be done as a cosmetic change in the plans.

      We currently know that the "Filters" dropdown on the AR plan show us the "Hierarchy" with which we can change the visibility of issue types on the plan from Highest to the lowest issue type in the hierarchy level. However, this only shows the "Hierarchy names" and not the issue types that are associated to that hierarchy level.

      The filter would look more easy to read and understand if the "Hierarchy names" also showed the associated issue types with it.
      For Eg:
      NEW - Feature, Objective
      Epic - Epic
      Story - Story, Bug, Task, Change Request
      Sub-Task - Sub-Task

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              1846b5d55690 Vaibhav Revankar
              Votes:
              5 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: