-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
None
Problem Definition
When we move an issue from backlog to an empty sprint, the RANK is not updated.
Steps to reproduce:
- Create a new board with 2 sprints
- Create at least 3 issues to backlog
- Move Issue 1 to Sprint 2
- Move Issue 2 to Sprint 1
- Move Issue 3 to Sprint 2 after Issue 1
- On Search for issues page, you will notice the order of the issues is
- Issue 1 -> Issue 3 -> Issue 2
- Issue 1 -> Issue 3 -> Issue 2
This is not sensible where the higher ranked sprint has a lower ranked issues.
Note
Noticed that this behaviour is caused by the act of moving an issue into an empty sprint is not changing the rank. When there's an issue in the sprint, the rank will then changed accordingly so the issues in the same sprint would have a similar rank.
See Unable to embed resource: RANK.webm of type video/webm
Suggested Resolution
RANK should adjust according to the sprint even the sprint is empty.
- duplicates
-
- Gathering Interest
[JSWSERVER-14869] Higher Ranked Sprint Should Have Higher Ranked Issues
| Workflow | Original: JAC Suggestion Workflow [ 3070024 ] | New: JAC Suggestion Workflow 3 [ 3662708 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2624480 ] | New: JAC Suggestion Workflow [ 3070024 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2326353 ] | New: Confluence Workflow - Public Facing v4 [ 2624480 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2043148 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2326353 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2031249 ] | New: JIRA PM Feature Request Workflow v2 [ 2043148 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 1599852 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2031249 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
| Description |
Original:
h3. Problem Definition
When we move an issue from backlog to an empty sprint, the RANK is not updated. _Steps to reproduce:_ # Create a new board with 2 sprints # Create at least 3 issues to backlog # Move _Issue 1_ to Sprint 2 # Move _Issue 2_ to Sprint 1 # Move _Issue 3_ to Sprint 2 after _Issue 1_ # On *Search for issues* page, you will notice the order of the issues is #* Issue 1 -> Issue 3 -> Issue 2 !Screenshot1.jpeg|thumbnail! !Screenshot1.jpeg|thumbnail! This is not sensible where the higher ranked sprint has a lower ranked issues. h3. Note Noticed that this behaviour is caused by the act of moving an issue into an empty sprint is not changing the rank. When there's an issue in the sprint, the rank will then changed accordingly so the issues in the same sprint would have a similar rank. See !RANK.webm! h3. Suggested Resolution RANK should adjust according to the sprint even the sprint is empty. |
New:
h3. Problem Definition
When we move an issue from backlog to an empty sprint, the RANK is not updated. _Steps to reproduce:_ # Create a new board with 2 sprints # Create at least 3 issues to backlog # Move _Issue 1_ to Sprint 2 # Move _Issue 2_ to Sprint 1 # Move _Issue 3_ to Sprint 2 after _Issue 1_ # On *Search for issues* page, you will notice the order of the issues is #* Issue 1 -> Issue 3 -> Issue 2 !Screenshot1.jpeg|thumbnail! !Screenshot2.jpeg|thumbnail! This is not sensible where the higher ranked sprint has a lower ranked issues. h3. Note Noticed that this behaviour is caused by the act of moving an issue into an empty sprint is not changing the rank. When there's an issue in the sprint, the rank will then changed accordingly so the issues in the same sprint would have a similar rank. See !RANK.webm! h3. Suggested Resolution RANK should adjust according to the sprint even the sprint is empty. |