Hi,
We have a few old sprints that were orphaned when a project was deleted. There are no tickets in that project but they're listed in current projects in sprint dropdowns in our Jira Cloud site
I’ve verified: - The REST API confirms the existence of current project sprints but calls to the old board ID (returning `rapidViewId` error) confirm that board no longer exists. JQL `Sprint in ("<old sprint name>")` returns “Sprint with name does not exist or you do not have permission to view it.”
So it seems these are orphaned sprint records left behind by a deleted board.
I've followed the workaround captured against https://jira.atlassian.com/browse/JSWCLOUD-11263 plus those comments left by others but to no avail.
Does anyone have any ideas what else could be done?
As we're on the Free Jira Cloud plan, I can’t open a support ticket for someone with backend access to do the cleanup because the workaround didn't work.
You’re correct, when a board is deleted, its sprints can remain in the system as “orphaned.” Since you’re on the Free plan (no Atlassian support), here are the two main workarounds that usually work:
There’s no direct UI option to bulk-remove orphaned sprints.
Hope this helps!
Thanks Christos! I tried the first option but the sprint wasnt listed. I assume they have an interal ID which doesnt match hence why it's not displayed. this would make sense for security reasons should a project be deleted then at some point in the future someone creates a new Project and inadvertently ressurrects old data.
It was a team-based project, we aren't using company-managed scrum projects.
The REST API method I tried but the orphansed sprint (which was active) isn't being associated with the board of the new project with the same project key.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Lets dive into it @Shahbaz Hafeez
The issue here is that team-managed projects complicate things because they don’t have the same backlog/sprint management options as company-managed projects, and orphaned sprints often lack a valid board association.
Why the workaround fails for team-managed projects
What you can still try
Let me know if it worked!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.