Open issues

Order by Priority
  1. Suggestion
    JSWSERVER-24818Allow Hierarchy flexibility between levels
  2. Suggestion
    JSWSERVER-4669Swimlanes for each value in field
  3. Suggestion
    JSWSERVER-5680As a user, I want to mark certain boards as favorites so I can find them in my list of boards more easily
  4. Suggestion
    JSWSERVER-7265As a user, I want to make estimates visible on cards in Kanban board
  5. Suggestion
    JSWSERVER-7393Access quick filters via REST API
  6. Suggestion
    JSWSERVER-10191Please allow to add scripted fields to the issue details view
  7. Suggestion
    JSWSERVER-10762Create a dashboard gadget for the Velocity Chart
  8. Suggestion
    JSWSERVER-11871As a user, I'd like to know who is the sprints creator
  9. Suggestion
    JSWSERVER-15993Make the Portfolio "Parent Link" field available on the Board Issue Detail View
  10. Suggestion
    JSWSERVER-16744Adding custom columns to Release Page
  11. Suggestion
    JSWSERVER-19959Add granular permissions relating to version control
  12. Suggestion
    JSWSERVER-20097JQL search for issues added and removed from a sprint
  13. Suggestion
    JSWSERVER-21245Ability to add custom columns in release page (view)
  14. Suggestion
    JSWSERVER-24776History Action Log for Advanced Roadmaps Plan (Portfolio) changes
  15. Suggestion
    JSWSERVER-25190Allow Advanced Roadmaps to Group by any custom field
  16. Suggestion
    JSWSERVER-25932Allow User to Enable/Disable Sticky Comment on Client Side
  17. Suggestion
    JSWSERVER-26402Advanced Roadmaps: New "View Manager" Role Request
  18. Suggestion
    JSWSERVER-25077Add Original Story Points field to Portfolio new experience
  19. Suggestion
    JSWSERVER-25882granular permissions for managing DVCS account for GitLab.
  20. Suggestion
    JSWSERVER-26384Add support for GitHub Enterprise Cloud environments hosted under *.ghe.com subdomains
  21. Suggestion
    JSWSERVER-10651Ability to bulk edit using sprint name rather than sprint ID
  22. Suggestion
    JSWSERVER-12599Allow sprint names in Bulk Change > Change Sprint
  23. Suggestion
    JSWSERVER-14931Disable or limit the "Create Branch" option
  24. Suggestion
    JSWSERVER-15655Ability to add columns to Epic Issue list on Epic
  25. Suggestion
    JSWSERVER-15973Turn off "Sprint scope will be affected by this action" message
  26. Suggestion
    JSWSERVER-21020As an Enterprise Admin, I want to install Jira on SELinux with Atlassian guidance
  27. Suggestion
    JSWSERVER-24905Ability to disable Jira notifications when committing plan changes
  28. Suggestion
    JSWSERVER-25115Milestones
  29. Suggestion
    JSWSERVER-25222Export plan as PDF
  30. Suggestion
    JSWSERVER-25253Add possibility to unshare a team.
  31. Suggestion
    JSWSERVER-25306Dashboard Gadgets for Advanced Roadmaps
  32. Suggestion
    JSWSERVER-26315The Dark Theme Mode is not supported by Advanced Roadmaps For Jira
  33. Suggestion
    JSWSERVER-26031Provide support for Pgpool-II active-active configurations
  34. Suggestion
    JSWSERVER-25121Add Original Estimate to Advanced Roadmaps New Experience
  35. Suggestion
    JSWSERVER-25925MySQL default auth plugin
  36. Suggestion
    JSWSERVER-13029Ability to see Sprint start and end dates in search results in issue navigator
  37. Suggestion
    JSWSERVER-20741Ability to configure quick filters to function as OR searches instead of AND searches
  38. Suggestion
    JSWSERVER-25116Plan should use Issue Resolution rather than Issue Status Category to determine when to remove issues
  39. Suggestion
    JSWSERVER-25193Release the "duplicate plan" feature for Jira Data Center
  40. Suggestion
    JSWSERVER-25247Portfolio Team Avatar
  41. Suggestion
    JSWSERVER-21581Limit the dates to fetch DVCS data
  42. Suggestion
    JSWSERVER-21773As a Gitub admin I would like to receive fewer API requests to grab user information
  43. Suggestion
    JSWSERVER-9554Customisable panels in Agile Backlog
  44. Suggestion
    JSWSERVER-11952Ability to configure a default board to show for a project
  45. Suggestion
    JSWSERVER-11992As a Jira Software user, I would like to be warned when moving issues which are in a sprint
  46. Suggestion
    JSWSERVER-15615Remove issue from Sprint before moving it to another project
  47. Suggestion
    JSWSERVER-25134Allow to show completed issues in schedule and reports pages
  48. Suggestion
    JSWSERVER-15634Duplicate sprint names creating conflicts
  49. Suggestion
    JSWSERVER-21676Introduce auth token refresh for github user tokens (ghu_) for DVCS integration
  50. Suggestion
    JSWSERVER-25232Add the ability to export Dependencies Report in Advanced Roadmaps
Refresh results
1 of 2932
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-24818

Allow Hierarchy flexibility between levels

    • 2
    • 13
    • 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

          Form Name

            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: