-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
5
-
8
-
When a new JIRA issue is created (particularly Stories and Bugs), it should appear at the top of the Rapid Board Plan Backlog, so that it's more likely to be seen by project planners.
- is related to
-
- Closed
-
- Gathering Interest
- is superseded by
-
- Gathering Interest
- was split into
-
- Gathering Interest
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
- relates to
-
LOLCATS-431 Loading...
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-5368] New issues to top of backlog
+1
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.
NO 
Sorry, but new issues should go to the bottom of the Backlog. They haven't been reviewed, or groomed, or ranked, or estimated or been through any of the planning sessions. They should be a new entry to the list, at the bottom, until then. And if you are Kanban, it is even more important they start at the bottom.
+1