nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issues' sprint field keeps track of previous sprints when moving it to the next sprint

Itay Keller_vqtase

We encounter this not clear phenomena:

When we close a sprint, we are asked what to do with the non-completed issues.

When we ask to move them to the next sprint, their "Sprint" field will now have 2 values: The new sprint, but also the prev sprint.

And if we won't complete them in the second sprint and move them to the 3rd sprint, the sprint field will now have 3 value: Sprint 1, Sprint 2 and Sprint 3.

We assumed that once we will move the non-complete issues to the next sprint, it will only have the value of the current sprint.

Is this "sprint history" a feature, a bug or something from our configuration?

Accepted answers

Jack Brickey

This is by design.

All comments

Jack Brickey

This is by design.

Itay Keller_vqtase

Do you know what is the business logic behind it?

Jack Brickey

While I have not read it anywhere, I’m sure it is to retain history showing where first committed. You could remove the older sprint if wanted.

Travis Lander

How do you remove the older sprint? I have this same issue - where I complete a sprint and move items to a future sprint. When doing so, the issue does not appear in that sprint and the only way to track down the issue is from links in other locations.

Does anyone know how to have noncomplete issues take ONLY the sprint you are moving the issue to in the sprint field OR have it so that the issues actually appear?