Unwanted Sprint Duplications across projects!

[Oliver Snow]

I have two projects - let's call them project A & project B - that seem to be sharing a Sprint. These projects and sprints should be completely separate. But, if I change the name/description of the sprint in project A, the same Sprint name and description are seen in project B!

However, the lists of issues visible in the sprint(s) in project A and project B are different. Project A sprint shows only issues from Project A, and B has issues from B only.

How is this possible? And how can I fix this?

Additional information: project A is being run by a team in another country using a non-English version of Jira. I noticed that I had a problem when displaying a burndown gadget for the English project B - the graph labels were in the language of project A!

Somewhere, the wires are crossed.

[Petter Gonçalves · Accepted solution]

Hello Oliver,

Welcome to Atlassian community!

The displaying of the same Sprint in different JIRA projects is expected in JIRA if the boards return issues in that Sprint. 

Basically, sprints are considered unique entities and are not related to projects but to issues. Let me give you an example:

Suppose you have the following setup:

Project A with Scrum Board A and Sprint A and Project B with Scrum Board B.

1 - If you move an issue which was included in Sprint A from Project A to Project B

2 - Or add issues from project B in Sprint A

The Sprint A becomes visible on Scrum Board B.

This happens for both open and closed sprints, and also affects all the reports related to sprints on Scrum Board A and Scrum Board B.

In both scenarios above, the sprint value remains the same. All projects which include the target issue will display the sprint that the target issue belongs to. Since the filter for Scrum Board B returns issues included in Sprint A, then the Sprint will be displayed on the board and in any relevant reports.

Since this is not very intuitive for end-users, we have raised the suggestion below as well:

- As a JIRA Agile user, I would like to be warned while moving issues which belong to a sprint

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

To prevent this from happening, you must clear the Sprint field for the issues in that are returned by the Board B or configure the filter (Board settings > Edit filter query) to don't return these issues with the JQL parameter below:

sprint != "sprint A"

For changing the value for multiple issues, follow the instructions in the Modifying Multiple (Bulk) Issues article.

Let me know if you still have any questions.

[Oliver Snow]

Thank you. That was helpful, but as you say, not obvious/counter-intuitive. We ended up with a team deleteting a sprint and its data because this was not understood. Agree that warnings "Are you sure... :consequences" should be given before a Jira user can proceed.

[Petter Gonçalves]

You are welcome, Oliver.

I completely agree with you that an alert should be placed to avoid unexpected behavior. Hopefully, this feature request will be addressed in the next releases.

Have a nice weekend.