Wrong sprint name is being displayed in the Issue Navigator

[Jillian Ahn Seymour]

Hi all,

I am encountering an issue with a set of tickets that were assigned to a given Release/Fix Version. They are showing the wrong sprint associated with them. 

These tickets were originally part of an inactive sprint ("The Important Sprint 2", a placeholder sprint), then got moved into our active sprint (called "Under Pressure"). We then completed that active sprint, so the board was closed out. Now, when I go to look at this release version's tickets using the Issue Navigator (Releases > Important Sprint 2 > View in Issue Navigator), it is showing the wrong sprint entirely. Under Sprint, it shows "Features", another inactive sprint, instead of "Under Pressure", the correct and recently completed sprint. 

Now, when I go to the Backlog and expand the sprint "Features", none of these tickets can be found (I am guessing because they are done). 

Any idea on why these tickets are pointing to the wrong sprint?

Thanks in advance!

[Trudy Claspill]

Hello @Jillian Ahn Seymour 

Welcome to the Atlassian community!

In Advanced Issue Search are you able to search for issues using the sprint name "Under Pressure"?

sprint = "Under Pressure"

When you start typing in the sprint name you will be shown possible matching sprint names. When you select one the JQL will show the numeric sprint ID rather than the name.

[Jillian Ahn Seymour]

Hi @Trudy Claspill thank you for your reply.

I am indeed able to search for issues using the sprint name "Under Pressure". 

My issue lies in the fact that the incorrect data are being displayed. When I am attempting to look at all of the tickets assigned to a certain release version, the issue navigator is showing an incorrect past sprint name in the "Sprint" column ("Features" when really it should say "Under Pressure" or "Important Sprint"). 

[Trudy Claspill]

In Advanced Issue Search when you search for issues using sprint = "Under Pressure" is it listing all the issues you expect?

From what you've shared when you are viewing a particular issue the system is stating

- in the issue history that the issue wasn't assigned to the Under Pressure sprint but was assigned to the Features sprint

- in the issue navigator it is showing the "wrong" sprints associated with the issue

I wanted to ascertain if you search for issues based on the "right" sprint, does that show the expected issues? I'm trying to understand if extent of where "wrong" data is displayed.

Jira doesn't generally spontaneously assign "wrong" values to issues, or randomly assign issues to sprints. If the issue details show unexpected sprints, and the search by sprints shows the same issues, then somehow the issues were in fact associated to that sprint. The next step is to try to figure out how that happened.

Could the "right" sprint have been renamed, making it appear that the issue was assigned to the wrong sprint?

Could the sprint assignment have been done by an Automation Rule? You can click on the Rule Executions field under Details in an issue to see the history of rules run against that issue. Is there a rule execution that corresponds to the timestamp when the issue was assigned to the "wrong" sprint?

Could the sprint assignment have been executed by a workflow transition post function? Was there a change of status for the issue at the same time?

Could the sprint assignment have been executed by a Listener? Do you have any Listeners defined for your Jira instance?