Jira shows Sprints twice on Team-managed software projects [NO FIX YET]

[Dimas Oliveira]

Someone knows how to deal with this annoying behavior on Jira???

On a Team-managed software project, all the sprints are show twice (sprint combo box on issue creation/edition) as bellow:

Sprints

• Go Horse Festival    [this was an orphaned one, fixed already]
• foo / Sprint 23
• bar / Sprint 13
• Go Horse Festival (duplicated) [this was an orphaned one, fixed already]
• foo / Sprint 23 (duplicated)
• bar / Sprint 13 (duplicated)

Besides the issue above, there is one extra Sprint that I cannot remove from the list (I've checked all projects, the sprint does not exists in any of them) [FIXED]

I really appreciate any direction.
Thanks in advance.   

[Bill Sheboy · Accepted solution]

Hi @Dimas Oliveira 

Would you please post an image of what you are seeing for the list of sprints on the issue create view?  That may provide context for the community to answer.

For the orphaned sprint, that can happen when a sprint was created for a board/project and the board/project have since been deleted, as described in this defect: https://jira.atlassian.com/browse/JSWCLOUD-17547  There are a set of work-around steps to remove the orphaned sprint documented in the defect.

Kind regards,
Bill

[Dimas Oliveira]

image and extra info added, thanks

[Dimas Oliveira]

The orphaned sprint is gone! Thank you.
Doing the workaround to get rid of it I found that the duplicated sprint list only occurs on Team-managed software projects (I will update the question).

[Bill Sheboy]

Thanks for the image!

In the image, you have hidden the board names.  Are those duplicates for the same or different boards (in different projects)?

If for different projects, there is a known issue where the dropdown does not filter for a specific project.  The suggestion to fix that is here: https://jira.atlassian.com/browse/JSWCLOUD-11814

If for the same project, I just found an open defect for this symptom, which you can vote for/watch to see progress on the fix: https://jira.atlassian.com/browse/JSWCLOUD-20735

[Dimas Oliveira]

@Bill Sheboy thank you for the assistance, it seems that this behavior could be fixed by 2030... till there we may create a browser plugin to avoid this annoying bug.

Best regards.