-
Bug
-
Resolution: Timed out
-
Medium
-
None
-
6.3.2
-
JIRA 5.2.8
JIRA Agile 6.3.1
-
6.03
-
Severity 2 - Major
-
Planned/future sprints are showing up in other teams boards who are not recognizing the sprint and closing them on the other team.
Prerequisites:
Each project has a PM who looks after the backlog of their project, but they both have admin access between the two projects.
- Project A (PRJA)
- Contains Component 1
- Contains Issue PRJA-1
- Contains Issue PRJA-2
- Project B (PRJB)
- Contains Component 2
- No initial issues
- Agile Scrum Board 1
- Filter: project = "Project A" and component = "Component 1"
- Agile Scrum Board 2
- Filter: project = "Project B" and component = "Component 2"
- Contains a sprint called Halloween Sprint
Steps to reproduce:
- Create a sprint in Board 1 called Sprint 1
- Add PRJA-1 to Sprint 1
- Add PRJA-2 to Sprint 1
- Move issue PRJA-2 to Project B (PRJB) / Component 2
- PRJA-2 is now PRJB-1
- Sprint 1 will now appear in Board 2
- Move PRJB-1 to Halloween Sprint in Board 2
- Sprint 1 will still appear in Board 2 and show as empty (even though there is 1 issue in Sprint 1 on Board 1
- The PM for Project B is able to close out Sprint 1 on Board 2 even though the sprint doesn't match any conditions to show on Board 2.
- relates to
-
JSWSERVER-9499 Moving issues can stop a sprint from being completed
- Closed