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; } } }

Sprint field removed when closing sprint

Mitch Coler

Has anyone else had an issue happening where when you close a sprint now it seems to remove a value from the sprint field? I just noticed this happen for the first time on a sprint we just closed today. When trying to add the value back it only shows options for active and future sprints now.

Is this possibly related to a new update Atlassian put out? I have not noticed this issue until very recently. In the history it does not show that any user nor the system removed the value and the issue does still show up within the Sprint Report. We are using the new UI maybe that is the issue?

Accepted answers

Andy Heinzer

Hi Mitch,

I don't believe this is a new feature. The sprint report is being generated at the time the sprint is closed. So the expectation with that report is that what you see there is what was in the sprint when it was closed.

However when you close a sprint, there is a question of "What happens to issues not completed in the sprint?" Since completed issues will tend to keep the sprint field value we aren't as concerned with them. But for issues that remained incomplete when that sprint closed, Jira Software will prompt the user that closed the sprint to figure out what to do with those incomplete issues. They can either place them in a future sprint (which changes the sprint field) OR they can add them back to the backlog (which actually clears that sprint field entirely).

So at least the report and this behavior is expected as far as I can tell so far. Is this not what you want to have happen to these issues?

I hope this helps.

Andy

All comments

Andy Heinzer

Hi Mitch,

So at least the report and this behavior is expected as far as I can tell so far. Is this not what you want to have happen to these issues?

I hope this helps.

Andy

Bhanu_79ebjq

That's a great explanation @Andy Heinzer

Tony Jacobsen

Hi I am new to using Jira, but am very proficient in Azure DevOps. Removing the sprint once a sprint is closed is unnecessary, and something I would like to see retained in the ticket. Everytime I search for closed issues, i wanted to see the sprint in which it was delivered. the sprint reports do not do a very good job of this, and the only way I have found it is to sift through the history. How do we request a feature change?

Josephine Choy

My org started to experience the same issue few weeks ago as well. We're researching to see if there's recent changes on how the sprint report get generated that may have impacted this. If anyone know the answer to where to look to disable the feature, please share!

Bryan_Park

did you find anything? my company is having the same issue. Thanks

Josephine Choy

Indeed we have; we noticed that if the sprint that's assigned to the task is a "future sprint" and not an "active sprint," the sprint will be removed upon the task is closed. (I assumed this is done to ensure the stats calculation is current for the sprint itself.)

So the solution is to either:

Make sure the task is assigned to an active sprint prior resolving and closing; OR
Set the sprint that the task is assigned to as "active"

Hope this helps!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud