-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Problem Definition
The epic view groups all the issue without epic at the bottom regardless of their rank, so from there you have no way of actually ranking them below
in this case, some of his story without epics are ranked above other with epics and gets scheduled before
in the story view the ranking should match the scheduling result
now there is definitely no way to massively re-rank issues at the bottom from either view.
Suggested Solution
It would be a sensible improvement suggestion to be able to (with some care) let a user rank all issues without epic at the bottom from the epic view.
Workaround
From the agile board (as it lets you group select and drag-drop) to re-rank those issues without epic actually below those with an epic
Having a JQL with all the stories without epic (and only those) should be an easy one
then can attribute them to a 'later' or 'triage' or just temporary epic
then in the portfolio epic view if you drag&drop that epic at the bottom it will re-rank all stories below the other
other solution would be to add those stories to a release and set it in the far future / after everything else
- relates to
-
- Closed
- links to
[JSWSERVER-24885] Ability to schedule stories without epics, always after stories with epics
Could i recommend a rewording of the summary of this issue from "Ability to On/Off Option To Consider Automatically Stories Without Epic To Be Considered" to "Ability to schedule stories without epics, always after stories with epics" ?
Thanks for the suggestions Sam, i will definitely try it. I think that even the implementation you have described here is still a 'workaround'. From my point of view, Portfolio just shouldn't schedule any stories that don't have epics before any stories that DO have epics.
If a story without an epic has a specific, manually assigned release or sprint date - thats different, then obey those requests. But if the release is basically 'later'... don't schedule those stories earlier.
I think that would be a reasonable business rule.
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