Editting Sprint + value

[Yatish Madhav]

Hi there

I would like some clarity on this please. On editting the Sprint field, what is the correct behaviour? I.e. Ideally we would like to have it update to only 1 sprint and if it automatically moves sprint to sprint, it should then have the "sprint it moved to" + the sprints it was on.

How do we achive that? OR is this the native behaviour that I am not understanding?

Thank you in advance.

Yatish

[Jack Brickey]

If you close a sprint then any incomplete issues will be moved to either the next sprint or the backlog. The sprint field will retain the sprint value where the issue was part of the committed plan. So if you have an issue that was committed to sprint 1, 2, 3 and 4 all four sprints would appear in the Sprint field unless manually removed.

[Yatish Madhav]

Hi @Jack Brickey 

Thanks for the reply

So I noticed the below on some moving tickets.

If I have an issue that has moved sprint to sprint to sprint - it keeps the previous sprints (expected)

But on manually editing the sprint field and clicking the X in the field it removes the current active sprint but retains the previous ones (showing 'None +12' as below) - I would expect it to only show nothing

And on re adding the current active sprint, it shows the current + 12 - I would expect it to only show the selected sprint and not the '+##'

See images below

On manually adding the "16 - 20 Aug" sprint

On manually clicking the X in the Sprint field

Please advise?

Thank you

[Yatish Madhav]

Hi

This is the other screen grab I needed to load here - I.e. If they are completed they display, this may be why I queried this.

Can this be configured at all in any way?

Thank you

[Yatish Madhav]

@Jack Brickey  any idea on this please?

[Jack Brickey]

So I think this is possibly more recent behavior to be honest.

I just did some quick testing and observed the same thing. It used to be, I think, that if you cleared the field it would clear them all. In fact, if you viewed the field it would show all of them in order. However, now it gives you the current Sprint +x as you noted.

So indeed I think that this is current expected behavior. Please note trying to remove old sprints ultimately breaks things specifically all of your reports and the velocity etc. So it may be that the Atlassian designers came up with this new solution to protect against that. Just a while theory on my part though.

[Yatish Madhav]

OK great - thanks for that input @Jack Brickey  - appreciate it. And yes, I have not thought about the reports that the sprints may affect. It seems the sprints is a very complex part of Jira.

I tried looking for specific documentation around this as well but could not find it. Will keep scouting for it.

Thank you again