We have two projects setup within Jira (application and Infrastructure) Each have their own set of sprints. As for today, when a sprint in one project was closed (infrastructure), it closed the sprint in another project (application). So when I go to fix the application sprint, it in turns changes the sprint in the Infrastructure project. There had been no issues until today. Is anyone else seeing this behavior?
Hello @Chris Thompson
Welcome to the Atlassian Community!
Per your description, it is possible that you are seeing the same Sprint on both boards, although the board filters restrict the same issues to be displayed on both boards. Please, allow me to provide you with some details on what can cause this issue so we can be on the same page:
Just like Boards, Sprints are completely independent, so it can be added to multiple Projects or Boards, just like described in the KB below:
Sprints appearing on multiple boards
That being said, a Sprint will be displayed on a board every time someone added a Sprint to any issue returned by that board filter. some scenarios that could cause this behavior would be if an issue is moved from one project to another without clearing the Sprint or if any issue is manually added with the Sprint of a different project.
The steps to fix it would be:
- Navigate to the board where the Sprints are unexpectedly appearing > board settings >Edit filter query
- At the end of the filter query (before the ORDER parameter), add the following parameter with the name of the Sprint that is wrongly displaying in the board and run the query, butdon't save it:
and sprint = yoursprintname- Now, you have the issues that are wrongly configured with the Sprint. You can change it to the correct Sprint of your project or clear the field, optionally using thebulk operation feature.
Now, if that is not the scenario you are facing, the only possible feature that could cause another Sprint to be completed when you click to complete a different one would be an Automation rule. Check under Project settings > Automation if there are any rules that would cause this issue.
Let us know if you have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.