Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Can you delete a sprint from one project without it being deleted from another?

We have 2 sprint teams, one on-shore and one off-shore, that work on an alternating sprint cadence. We recently made that change and split the sprints up. When I created the separate projects and sprints, I added the respective sub-projects, in which some are relevant to both teams. Now on each teams project page, under active sprints, there are both and you have to filter among them. Can I delete the irrelevant sprint from the project without deleting it entirely? 

1 answer

1 accepted

0 votes
Answer accepted
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 02, 2020

Hi @Samuel Justus,

Welcome to Atlassian Community!

Sprints are not tied to a specific project or a board, so if you remove it from one board you will remove it from all. The way you can remove it from one project without affecting other projects is to remove the sprint from issues that are associated with it. Depending on how many issues you have you could do this using bulk edit.

Thanks @Mikael Sandberg , however i'm not sure exactly what you mean by "remove the sprint from issues that are associated with it'. Could you please elaborate?

Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 02, 2020

I you open up an issue that is associated with the sprint you want to remove, you should see the Sprint field. Just remove the sprint from this field to de-associate the issue. Repeat this with all the issues that was moved to your second project that should not see the sprint. Or the other option is on the board, if the sprint is not currently active, just drag and drop the issues from the sprint back to the backlog or a different sprint.

But what if sprint is active? We have the next issue: created a task in a project A, but assigned it to an active sprint of a project B (by mistake). When realized it - changed sprint value to a correct active sprint of project A. After that we had to close the sprint of Project A and open a new one, but can't do it, because active sprint from project B is still shown in a backlog and perceived by project A as an active sprint (without any tasks inside it).



When trying to close sprint inside project A - it says that 75 issues will be affected (all of them are in project B). Very annoying...

@Anatoliy Uvarov were you able to find a good solution to this? We are experiencing the same thing. It's been super annoying and we seem to be in some loop where sprints from other teams show up in our project, we ensure they're empty and delete them, and then they're deleted for the other project. Sometimes they're active sprints, sometimes inactive. Unsure why this started happening recently.

Like Melissa Pather likes this

hi @Derick Johnson 

We solved this by creating a new sprint in project B and moving of all tasks there to make a connected sprint empty. After that - deleted both empty sprints. Not the best way to fix, but it worked.

Maybe it's a problem if the sprint already started, then even though you remove/fix all references to Project B, then the empty sprint is still displayed in Project B backlog because of history for burndown charts/reports etc..

Although I have my own radical theory that this didn't used to be a problem (Sprint would previously correctly disappear when empty in Project B and no sprint issues linked to Project B), and this new behavior was introduced when native roadmaps started supporting classic Jira projects (maybe some internal select mechanism was updated) :-).

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events