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

Sprints won't recognise Resolved issues

Chrys Piva

Hello,

I have created a custom flow for my issues and I noticed that when I Complete a Sprint it will transition all my resolved issues to the next sprint. This is extremely annoying.

After reading a few forum posts I seem to have found that the Resolution field needs to be not empty for it to be completed in a sprint (Why? - why not just use the status for that *shrug* ) So I have added a Resolution field with "Unresolved" and "Resolved" field values.

I have then created a rule for each transition that is supposed to modify the field to the appropriate value. I get a lot of warnings with no indication what is wrong. I verified my transitions are indeed setting the value of the Resolution field. But the sprint still will consider them as open issues.

I attached some screenshots to illustrate the problem.

Anyone knows what I am doing wrong ?

Accepted answers

Trudy P Claspill

Hello @Chrys Piva

Welcome to the community.

I think you have misunderstood.

A sprint does not evaluate the issues as completed based on the Resolution field. It determines that issues are completed if they are in a status that is mapped to the column farthest to the right on your board. It doesn't matter what the status is nor if there is a Resolution value, only that it is mapped farthest to the right.

Resolution is used by other types of reports, but it is not used by the "completed" evaluation that occurs when closing a sprint.

All comments

Trudy P Claspill

Hello @Chrys Piva

Welcome to the community.

I think you have misunderstood.

Resolution is used by other types of reports, but it is not used by the "completed" evaluation that occurs when closing a sprint.

Pramodh M

I believe the screenshot which you have shared and the Resolution field which is visible is the custom field

Make sure the Issue is in Done Category (Green) and the last column on the board

Here are reference examples from my board

1 - There are two Done Category Status - Done and Closed

2 - When I try to complete the Sprint it recognizes only the resolved issues with Done category and last column board issues

Let me know if you have any query

Thanks,
Pramodh

Chrys Piva

Oh I see - Okay so I moved the "Resolved" Column to the far right on the board.
Is it possible to have multiple columns considered as "Done" ?

In my workflow these 3 states
Obsolete - QA-Fixed and Resolved are considered "Done" states

I would expect the board to consider all three as completed issue types.

Trudy P Claspill

You will have to map all three statuses into one column - the column farthest to the right - in order for the sprint to consider issues in all those status as "completed".

Chrys Piva

when you say "You will have to map all three statuses into one column"

do you mean I should add a state to the workflow that is called i.e. "Completed"
or is there an actual way I am not seeing to merge the 3 states into one column on the board configuration itself ?

Fabio Racobaldo _Catworkx_

HI @Chrys Piva ,

within a sprint, a ticket is considered "DONE" if resolution is not empty and the status has been mapped in the last column on the right of your board.

Hope this helps,

Fabio

Trudy P Claspill

@Fabio Racobaldo _Catworkx_

You are not required to have a Resolution value for a sprint to consider an issue completed. You only have to have the status mapped to the farthest right column on the board.

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