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

Resolved issues being treated as open while completing sprints

Peeyush Rai

Hi Folks,

Our workflow forces a resolution to be set when the issue status is set to "verified" (of type done). However, when we clomplete sprints JIRA considers all the resolved tickets in the sprint as still open and moves them to the next sprint.

Is there a configuration we are missing due to which this is happening?

Accepted answers

Ste Wright

Hi @Peeyush Rai

Sprints do not utilise resolution or status as "done" - it's based on what is in the last column on the board. This allows flexibility for teams who might not consider deployment as "sprint done"

Is the issue status "Verified" in the last column on the right-hand side?

Ste

All comments

Ste Wright

Hi @Peeyush Rai

Sprints do not utilise resolution or status as "done" - it's based on what is in the last column on the board. This allows flexibility for teams who might not consider deployment as "sprint done"

Is the issue status "Verified" in the last column on the right-hand side?

Ste

Peeyush Rai

Thanks @Ste Wright I added the Verified column to the right of the board and it seems to have fixed the issue.

My understanding was the board is just a "View" to manage sprints (similar to backlog) and the workflow statuses and resolution should determine if an issue is complete or not. Hope this logic gets fixed in future, as it looks very fragile currently.

Ste Wright

Hi @Peeyush Rai

Awesome glad it worked!

The board is a visualisation of an issue filter, but allows for sprints (and their corresponding reports) to function.

However, I do think the logic makes sense. From a board perspective, the last column is completion - and this allows for flexibility in what is classed as "sprint done" vs "complete".

For example, if a team develops in 2-week sprints - but only releases every quarter - they can still get a report on "done" from each sprint, without needing to completely close an issue.

Ste

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-software

sprint

status

resolution