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

Changes to Rank of an Epic don't change the Rank of their child Stories.

XMLWordPrintable

    • 1
    • 2
    • 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.

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

      It seems I can change the rank of an Epic from within the Scope of a Portfolio plan - this is don't by selecting 'epic' and dragging an epic up or down relative to the other epics. This changes the relative rank of the epics.

       

      What doesn't appear to happen though, is any change to the rank of the child stories. I would expect that if I dragged a epic above another one, then it's enclosing stories should now rank higher than the stories of the epic that is now ranked lower.

      Is that supposed to work, or are there any tool sets I can use to make that happen?

      It seems difficult to sync the schedule suggested by Portfolio back onto a board, so that the priorities set in the schedule affect the order of work that is picked up from the board (in a Kanban style).

       

      Am I missing something?

            [JSWSERVER-25211] Changes to Rank of an Epic don't change the Rank of their child Stories.

            SET Analytics Bot made changes -
            Support reference count Original: 4 New: 2
            Marc Dacanay made changes -
            Labels Original: Plan-Roadmap jpos_1023 New: Plan-Roadmap jpos_1023 ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 979707 ]
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            Aakrity Tibrewal made changes -
            Component/s Original: Scheduling [ 36491 ]
            Component/s New: (Advanced Roadmaps) Plan - Roadmap [ 63498 ]
            Key Original: JPOSERVER-1860 New: JSWSERVER-25211
            Project Original: Advanced Roadmaps [ 16510 ] New: Jira Software Server and Data Center [ 12200 ]

            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
            Stasiu made changes -
            Labels Original: jpos_1023 New: Plan-Roadmap jpos_1023
            Mathias Richter made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 807104 ]
            SET Analytics Bot made changes -
            UIS Original: 32 New: 0

            Karen Wells added a comment -

            Once upon a long time ago, Portfolio did adjust the rank of tickets on backlog and kanban boards when ranking of epics was changed. This is no longer the case. It is one of the more powerful features for communicating priority to the teams that work from these boards and not from Portfolio/Adv RM (I'm getting used to the new name). Please give us the option to push priority/rank changes back to Jira and have them reflected in the boards. 

            Thanks!

            Karen Wells added a comment - Once upon a long time ago, Portfolio did adjust the rank of tickets on backlog and kanban boards when ranking of epics was changed. This is no longer the case. It is one of the more powerful features for communicating priority to the teams that work from these boards and not from Portfolio/Adv RM (I'm getting used to the new name). Please give us the option to push priority/rank changes back to Jira and have them reflected in the boards.  Thanks!

              Unassigned Unassigned
              2304b3a0b451 Josef Karthauser
              Votes:
              26 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated: