Problem Definition

When sprints appear on multiple boards, modifying the sprint in one project (sample A) such as edit/delete action, modifies the sprint on another (sample B).

The end user deleting the sprint in Sample A project may not be aware that they are deleting the sprint in Sample B project, which can mess up another team's work. 

Such behaviour are also explained in the below articles:

• Sprints appearing on multiple boards in Jira Data Center, Server, or Cloud
• Why does moving an issue between projects associate the sprint from the old project with the new one 

Suggested Solution

There are several suggestions that end users would like to prevent issues/confusion:

• Sprints should not be deletable by users who do not have access to the project where the sprint was created.
• Create a warning for the end user when editing/deleting a sprint can affect other projects (for example, sprint has Jira issues on other projects than is currently seen by the user)

Workaround

• To prevent sprints to be shared between projects, it is advisable to ensure that Jira issues have the correct sprint intended specific to a project.