-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
9
-
As per GHS-10472, as a JIRA Agile User I'd like to choose whether the issues I'm creating are added to the bottom or the top of the backlog, or if it should be added above the current selected issue.
Some users may think a new issue should put it to the bottom of the backlog to prevent accidentally giving the issue a priority while others may prefer the current behavior, so giving the ability to chose which suits better for the users would be great.
Current Behavior:
- When 1 or more issues have been selected -> rank the new issue after the lowest ranked selected issue
- When no issue is selected -> rank the issue at the top of where the plan mode is currently scrolled.
- When not on plan mode, new issues are ranked to the bottom of the backlog
- is duplicated by
-
- Closed
- is related to
-
JSWSERVER-10472 "Create Issue" Sets Rank Randomly
-
- Closed
-
- relates to
-
- Gathering Interest
-
LOLCATS-431 Failed to load
[JSWSERVER-10846] Ability to choose where new Issues will be added in the Backlog
Yes this does create a lot of churn for teams, and should be configurable per team board as they are best able to define the process where new should appear.
In absence of this, from a backlog management point of view, new items should always show up at the bottom as the lifecyle of a backlog item being to percolate up to the top through the process of refinement - that includes prioritization, detailing out the problem to chunking down the problem.
It would be nice if this could be a setting per project or board or something.
Proposal:
Introduce a new, 2-step sorting option, where the main sorting is performed based on priority, and the the items inside of a priority are sorted by rank.
Hans Wijnveen
added a comment - Alternatively, being able to automatically set the Rank of an issue after Accepting (as a Post Function) would also do the trick, I think.
Hans Wijnveen
added a comment - Alternatively, being able to automatically set the Rank of an issue after Accepting (as a Post Function) would also do the trick, I think.
I have a separate Kanban board for Refinement using Company Managed Software project type. All new issues with 'To Do' status are mapped to the "Backlog" of the Kanban board, and I would prefer new issues that need Refinement be added to the top of this board.
After completing the workflow for Refinement, the issues are then placed in the correct Rank in a Scrum board to be added to an upcoming Sprint.
It would be great to configure the default of where new issues are placed in the Backlog, regardless of the board you are currently on, so they can be quickly/easily added.