Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-24818

Allow Hierarchy flexibility between levels

XMLWordPrintable

    • 3
    • 15
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently, Advanced Roadmaps only allow issues to be related through direct levels within the configured Hierarchy.

      In some scenarios, customer's use-case request that issues are linked in a way that will bypass a direct Hierarchy relationship. For example, considering the following hierarchy:

      Initiative > Epic > Story > Sub-task

      The following scenario is currently not possible:

      • Initiative > Story
      • Epic > Story > Tasks > Sub-task

            [JSWSERVER-24818] Allow Hierarchy flexibility between levels

            Barış Türkkal added a comment -

            https://getsupport.atlassian.com/browse/PS-165493

            Barış Türkkal added a comment - https://getsupport.atlassian.com/browse/PS-165493

            Barış Türkkal added a comment -

            https://getsupport.atlassian.com/browse/PSSRV-115631

            Barış Türkkal added a comment - https://getsupport.atlassian.com/browse/PSSRV-115631

            Aakrity Tibrewal added a comment -

            Dear all,
            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            Robert Campbell added a comment -

            Yes, this correctly reflects my use case. In our case, we're attempting to implement a SAFe hierarchy. The hierarchy currently reflects Epic < Capability < Feature, etc. There are times where the Feature needs to link directly with the Epic, bypassing the Capability (large solution layer).

            Robert Campbell added a comment - Yes, this correctly reflects my use case. In our case, we're attempting to implement a SAFe hierarchy. The hierarchy currently reflects Epic < Capability < Feature, etc. There are times where the Feature needs to link directly with the Epic, bypassing the Capability (large solution layer).

              Unassigned Unassigned
              bpicarelli Benito Picarelli
              Votes:
              16 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: