-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
2
-
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?
- relates to
-
- Gathering Interest
-
- Gathering Interest
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-25211] Changes to Rank of an Epic don't change the Rank of their child Stories.
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!
Ok, that is working, but as I reported above if you change the rank of an Epic, it doesn't also change the relative ranks of the associated Stories 
. I don't know how to do that, but it's important so that we can adjust the ranks of stories on the boards by changing the priorities of the Epics (and similarly with changes to the Initiatives)
That should work out of the box, you just need to make sure you commit the changes back to JIRA.
It's more a matter of being able to use portfolio to adjust the ranks and then burn those changes back into the epic/stories so that the agile boards can be updated to follow the portfolio changes.
This seems to be related to https://jira.atlassian.com/browse/JPO-1842, where the proposal is to make it optional / configurable whether the scheduling algorithm shall use the rank of the Epics or the rank of the Stories for scheduling (should be configurable since there may be good reasons for why you want the ranking of the stories to not match the ranking of their Epics).
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