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

Resolution vs. status Done help

Ben Weisman

Hello,

I have a bit of an issue and need some help!

We've just set up a new system and are in our first sprint. In order to be able to track how quickly we're resolving our bug tickets the team wanted the resolution to be set to Resolved once the Dev work is complete. However, there are still 3-4 more statuses before it is moved to the Done column.

The problem is, I don't want these resolved tickets that are not yet in status 'Done' to leave the sprint. How do I fix this issue before we close the sprint??

Thanks.

Accepted answers

All comments

Nic Brough -Adaptavist-

Resolution does not affect the sprint tracking. The sprint simply considers the issues in the very last column to be "done"

Joe Pitt

I had a similar problem. I created a custom field select list for them to set when they moved the issue to the next step. Then if the test team failed the test it would go back to the dev team and the field would be cleared.

Ben Weisman

I don't believe this is the case? I'm pretty sure that unresolved tickets within the Done column carry to the next sprint. Which would mean that tickets marked resolved but NOT in the done column would disapear.

No?

@Nic Brough -Adaptavist-

Ben Weisman

Thanks for the reply. How does this help solve the tickets being removed from the following sprint though if they're marked resolved at the time but not in status Done?

@Joe Pitt

Trudy P Claspill

Are you working with a Team Managed project or a Company Managed project?

For a Company Managed project, I just tested these scenarios.

I can confirm that an issue in the right-most column that has the Resolution field empty (i.e. has an In Progress status) will be considered completed when the sprint is closed and will not be moved to the next sprint or the backlog.

I can confirm that an issues that has a Resolution value (and is in a Done status) but is NOT in the right-most column is considered incomplete at the end of the sprint and will be moved to the next sprint or the backlog per the sprint-closer's choice.

Nic Brough -Adaptavist-

Thanks for checking @Trudy P Claspill - I keep going back and doing the same test in case Atlassian quietly change it, every few months, just to reassure myself. I was about to do it again before answering Ben, but you've saved me the time!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud