Problem Definition
| What |
How |
Consequences |
| Issues mistakenly added to the sprint |
- Customer has sprints on different boards with similar name
- When a user opens an issue on edit mode and clicks on dropdown then all sprints will be listed
- User chooses the wrong sprint (dropdown doesn't have reference to its board)
|
The board A will display a sprint that was created on board B.
If the user doesn't have access on all projects returned by the other board B then he won't be able to start and complete that sprint on board A. |
| Issues mistakenly added to the sprint |
- Customer has sprints on different boards with reference to the project name
- User mistakenly add the issue on a sprint that belongs to another board
|
The board A will display a sprint that was created on board B. # The user doesn't want the sprint on board A and delete it
-
- The team on board B will lose their work.
- The user assigns more issues to the sprint and start/complete the sprint
- The team on board B will have their sprint started without knowing why that happened. Their remaining work will be moved to backlog.
- The user renames the sprint on board A to match the project name
- The team on board B will be confused about the change
|
| Issues mistakenly added to the sprint |
- Customer has sprints on different boards with reference to the project name
- User mistakenly add the issue on a sprint that belongs to another board
- User closes the issue
|
The board A won't display the sprint that was created on board B.
If the user creates a new sprint on board A then it will follow the name pattern for sprints on board B and he won't understand how it happened. |
| The team board has different projects in order to verify the individuals backlog |
- The team A works on project A however its developers are also working on project B. The manager for team A needs to have a clear view of the developers time allocation on board A and so he uses the filter Project = A or assignee in (User1, User2)
|
If the board's A the next sprint is from board B, the users won't be able to start the sprint from project A. |
| The team board has different projects in order to verify the individuals backlog |
- The team A works on project A however its developers are also working on project B. The manager for team A needs to have a clear view of the developers time allocation on board A and so he uses the filter Project = A or assignee in (User1, User2)
- User closes the sprint on board A
|
If there are open issues then the pop up to close the sprint will suggest moving the issues to the next sprint which might belong to project B |
Suggested Solution
Enable the option to restrict the scope of sprint to projects (or boards)
Suggestion
A suggestion would be to have sprint ID's unique to each project