Recently completed sprint missing from Reports drop-down Sprint List?

[Craig Storms]

Pretty much title says it all. We completed a sprint, the last of the project, and in looking at the Burnup Charts this last sprint is not shown - cannot view reports for this last sprint.  If I copy and pasted the Sprint Title in Jira does not resolve the match. However I can do queries on the sprint no problem.

There is no new active sprint.

Any suggestions on how to get this to show in the Reports drop-down list of Sprints?

[Shannon S]

Hi Craig,

Can you confirm the Sprint was using a Scrum board and not Kanban?

Regards,

Shannon

[Craig Storms]

Hi Shannon ... yes it was using a scrum board. 

[Shannon S]

Thank you for confirming, Craig.

We need to see your Cloud instance itself to determine the issue. Therefore, I am creating a support ticket now so we can obtain that information from you.

Once the issue is resolved there please feel free to come back here and share the resolution as it will help users in the future.

Regards,

Shannon

[pranayv]

Having the same issue. The cloud version is not showing me all the completed sprints in the drop down and I am using a scrum board and not kanban.

I do not see a resolution for the above issue. Looks like it was reported on July 2 by Shannon. 

What's the plan? 

[Shannon S]

Hello @pranayv,

I have a summary here for what was the cause of Craig's issue:

Sprints are dependents on issues, not projects or board strictly. With that in mind, it's possible for a sprint to be shared between boards "wrongly". This can happen if, for some reason, a user add by mistake an issue to a sprint.

If this doesn't help you to determine the issue with your Sprint, I would recommend that you create a ticket with our Cloud Support Team. They will be able to have a look and let you know what is the issue that is causing the same for you.

Let me know if you have any trouble.

Regards,

Shannon

[Craig Storms]

Hi Shannon thanks for the follow up. Not really sure what this means:

"Sprints are dependents on issues, not projects or board strictly. With that in mind, it's possible for a sprint to be shared between boards "wrongly". This can happen if, for some reason, a user add by mistake an issue to a sprint."

"Wrongly" doesn't have any specific details to help me identify what is "wrong" with a spring configuration. Obviously all sprints contain 'n' issues. The example given "a user add by mistake an issue to a sprint" doesn't tell me much. Issues can be added or removed during an active sprint. What exactly is the "mistake" that is occurring?

This is now over a year old. Obviously we've moved on and are just dealing with what appears to be a Jira quirk to our team. If there is something we are doing that is causing this to occur I would welcome clarity to avoid it in the future.

Thank you.

Craig

[Shannon S]

Hello @Craig Storms,

Apologies for the confusion, but @pranayv was asking what became of your case that you raised with support over a year ago. I was summarising what the Jira Software engineer told you in your case.

The engineer had suspected that what caused this issue was that a user incorrectly added an issue to a Sprint which caused it not to display. It's hard to say for sure what the issue was on your particular case without being able to see your Sprint or your boards. Back when I worked on Jira Software, I did see a variety of cases that caused issues such as this, for example, an issue from another project other than the one that the Sprint was focusing on.

For this reason, I would recommend if anyone is not seeing the expected behavior from a sprint or Kanban board on Cloud to please raise it with the Cloud Support Team. There, we will be able to get a hands-on look at your instance and determine the exact reason for the problem.

Regards,

Shannon