Why do my Stories show multiple Sprints?

[Parimal Zaveri]

I recently joined my company - which has been using JIRA Cloud for scrum based software dev.

I notice that many stories have multiple values in the Sprint field - apparently its recording all sprints that a Story was ever in. For example, if a story was originally planned for Sprint 1, then got moved to Sprint 2 - it shows "Sprint 1, Sprint 2" as the values for the Sprint field.

I just want the currently assigned Sprint - blank if its in the backlog

Is this a config setting? Are there multiple Sprint related fields and we just need to expose the correct one?

[Tyler Brown]

Hey Parimal,

There is only the one Sprint field by default.

You can clear all of the previous values from the Sprint field.

Going forward as long as you remove all Stories that were not completed before closing the Sprint they will not keep the old values.  The only time they will carry the value forward is if the Sprint is closed and they are moved (either to the backlog or the next Sprint).

Hope this helps,

Tyler

[Parimal Zaveri]

@Tyler Brown Thanks for your reply.

Moving forward, I will make sure things are done in the correct order - moving stories first, then close sprints

How do I clear the previous Sprint values?

[Tyler Brown]

You can preform a bulk change on all issues.

Search for everything that's not closed and not in the current Sprint and then edit the "Sprint" field but leave it blank and that should sort everything out.

[Ann Guerra]

Can this be fixed?  Seems like a bug not a feature.  I don't see a use case where we would want to close a sprint and let Jira move the stories to the backlog or the next sprint AND also want to keep all the prior sprints it was ever in.   

If there is a use case for when we would want this to happen, please tell me?  Takes away from the usability of an otherwise nice feature.

[Abhigyan Singh]

Yes, carrying multiple sprint names in the same sprint box is a little counterintuitive.

If I want to know the current sprint of an issue I'll look at its Sprint value, and seeing two sprints there won't make sense.

If ever we want to see the previous Sprints an issue was in we could always view its History. 

Cuz Sprint maps to a particular date range in actual time, showing multiple sprints means the same issue is in different time periods simultaneously.

[Matthew Mallard]

You could create a new field to hold the latest/last sprint. Then, through Jira Automation, you can set it with a smart value of {{sprint.last.name}}