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

Mark multiple status as Set Resolution in Board setting?

David Leal_28ge8x

We have a project where we need to identify when the user story is READY (Requirement Phase) and then when it is finally delivered (DONE) in Development. We have defined a Scrum Board with different columns to see the progress across multiple phases. The team documenting the user story would like to see the progress they made taking the user story from TODO and putting it into the status of READY. We are wondering if marking the option: Set Resolution in the state READY in column READY will solve the problem. If not, is there any way to have Burndown Chart for representing the evolution of the stories from TODO -> READY and then another burndown chart to see the evolution of the stories from IN-DEV -> DONE for example?

I was not able to find information about what does set resolution mean in the context of defining the Board? or even if it is possible to specify the final state in the Burndown Chart.

Accepted answers

Fazila Ashraf

Hi @David Leal

Setting the resolution in JIRA would actually mean that the task is completed. The resolved date and many other fields are populated based on this set resolution.

If your Story has just completed the requirements phase then you shouldnt be setting the resolution till the story is deployed and done.

And about burndown, what is the estimation and tracking statistic used in the board? What information do you want to deduce from the reports? Like how long it took to change statuses?

All comments

Fazila Ashraf

Hi @David Leal

Setting the resolution in JIRA would actually mean that the task is completed. The resolved date and many other fields are populated based on this set resolution.

If your Story has just completed the requirements phase then you shouldnt be setting the resolution till the story is deployed and done.

And about burndown, what is the estimation and tracking statistic used in the board? What information do you want to deduce from the reports? Like how long it took to change statuses?

Nic Brough -Adaptavist-

Just to be clear on the boards, resolution is the measure plain Jira uses for "issue needs no more work". Boards define "issue is in the last right-hand column on the board" as "done"

You can set up different boards to map different status to their "done" columns to get different measures of burn down.

David Leal_28ge8x

@Fazila Ashraf thanks for your rapid response. Strictly speaking, the story is not done, but we would like to track when it was ready. The team in charge of documenting them has a board, but they have the standard workflow: TODO, IN PROGRESS, DONE. Now the can see progress in the Burndown Chart. We would like to change the workflow to something like this: TODO, DOCUMENTING, READY, IN DEV, IN QAT, DONE. The intention of my question was if I mark, for example, the status READY in the corresponding column of the board Set as Resolution field, can we achieve that we can see in the Burndown Chart the journey from TODO-> READY but also from TODO->DONE and from READY->DONE for example.

@Nic Brough -Adaptavist- I get this when we mark in the board just one column with a status as resolution, I would like to understand the scenario when we can mark more than one status as resolution.

Nic Brough -Adaptavist-

Ok, there is no "mark status as resolution". Resolution is a field, status is an indicator of where an issue is in its workflow.

You can say "as we go into this status, set the resolution (or clear it)", as part of a transition, either via screen or post-function, but that's a logical procedural thing that you have to do.

The boards make this easier - there's a check box for "set resolved" which adds the post-functions for you (set resolution on into the status/column and clear it on moving to ones that are not).

But setting and clearing this separately in different boards can confuse it. You should decide on a clear and simple mapping - each status really ought to fall into either "resolved" or "unresolved" for your data to work.

None of that affects burndown. All that matters for burndown is the right-hand 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

jira

cloud

jira-cloud