Hi there,
in my JIRA Software Cloud account I had some old projects with their boards running in the past. These old projects were deleted long ago but it seems that boards linked to these projects got stucked somewhere in Atlassian universe.
I see these stucked boards (highlighted in below screenshot) in JIRA overview but I am unable to delete or even view their detail.
As you can see the Locations fields of stucked boards are undefined and there is no clickable board name.
Also I see scrum sprints from these stucked boards in my current JIRA issues so it is a bit confusing during managing current tasks/sprints.
I tried to search for these boards in JIRA general search field so it makes boards clickable (workaround which I found in Atlassian Community).
After opening board detail from search panel I was asked by JIRA to select new Location for this board. So I create new TEST project where I wanted all stucked boards to be moved.
But after that JIRA told me "Sorry, I cannot do that because something went wrong":
I want to delete mentioned boards so my current project won't be clogged with old boards and sprints. But I am not able to move over the ERROR: 1PY5X6V.
Have someone been facing similar issue?
have those deleted projects by any chance been next-gen projects?
I encountered the same and found a bug opened with Atlassian addressing this topic:
What helped in my case was to restore the project, delete the corresponding board and delete the project again, however the bug reports refers you to Atlassian Support - so it might depend on how the cirumstances are especially in your cloud site.
Regards,
Daniel
Hi @Daniel Ebers ,
in my case I am unable to restore old project.
There is no project in my trash/archive to be restored.
Anyway I forwarded error code to Atlassian support 🙂
Jirka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That error code is just a reference for Atlassian support to be easily able to find your system and the errors in the Cloud logs.
You need to take this to Atlassian support if it persists, raising it at https://support.atlassian.com/contact
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.