-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Original summary: Need a way to distinguish between new tickets and previously prioritized tickets
Because of https://jira.atlassian.com/browse/GHS-6905, it's now very difficult to keep the Backlog prioritized. People implicitly prioritize their tickets inadvertently by adding them into the middle of the backlog.
For my team, it's important to have a distinction between a Backlog, which is prioritized, and a list of new bugs which have not yet been prioritized.
I'd like to suggest adding a new group separate from the backlog, where all new tickets go. It could be called something along the lines of "Needs Triage" or similar to indicate that these bugs have not yet been prioritized. New bugs would go into this grouping, until they get prioritized in the backlog.
- duplicates
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-10496] Distinguish new issues and previously prioritized issues
| Workflow | Original: JAC Suggestion Workflow [ 3068923 ] | New: JAC Suggestion Workflow 3 [ 3662374 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2625790 ] | New: JAC Suggestion Workflow [ 3068923 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327548 ] | New: Confluence Workflow - Public Facing v4 [ 2625790 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2044390 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327548 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032608 ] | New: JIRA PM Feature Request Workflow v2 [ 2044390 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 735878 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032608 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
| Description |
Original:
Because of https://jira.atlassian.com/browse/GHS-6905, it's now very difficult to keep the Backlog prioritized. People implicitly prioritize their tickets inadvertently by adding them into the middle of the backlog.
For my team, it's important to have a distinction between a Backlog, which is prioritized, and a list of new bugs which have not yet been prioritized. I'd like to suggest adding a new group separate from the backlog, where all new tickets go. It could be called something along the lines of "Needs Triage" or similar to indicate that these bugs have not yet been prioritized. New bugs would go into this grouping, until they get prioritized in the backlog. |
New:
Original summary: {{Need a way to distinguish between new tickets and previously prioritized tickets}}
Because of https://jira.atlassian.com/browse/GHS-6905, it's now very difficult to keep the Backlog prioritized. People implicitly prioritize their tickets inadvertently by adding them into the middle of the backlog. For my team, it's important to have a distinction between a Backlog, which is prioritized, and a list of new bugs which have not yet been prioritized. I'd like to suggest adding a new group separate from the backlog, where all new tickets go. It could be called something along the lines of "Needs Triage" or similar to indicate that these bugs have not yet been prioritized. New bugs would go into this grouping, until they get prioritized in the backlog. |
Despite being older than GHS-11139 I'm closing this as a duplicate since there are more votes on that Suggestion.
Please follow GHS-11139 for further progress and add any additional comments there.
Kind regards,
Martin
JIRA Software