Mark multiple status as Set Resolution in Board setting?

David Leal
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 29, 2018

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.

1 answer

1 accepted

1 vote
Answer accepted
Fazila Ashraf
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 29, 2018

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-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 30, 2018

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.

Like David Leal likes this
David Leal
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 30, 2018

@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-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 1, 2018

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.

David Leal
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 1, 2018

@Nic Brough -Adaptavist- now it is more clear for me. Then there is actually only one final state per workflow (let's say DONE). Marking the Set resolution just will indicate a post-function that needs to be defined one the issue reaches the given status. 

Screen Shot 2018-12-01 at 4.47.53 PM.pngTherefore adding, for example, a new Column READY with the corresponding status and marking it as Set Resolution, just will imply that we need to define a post-function and the Burndown chart will take into consideration the issues that ended in DONE status.

Thanks!

M Vijay Kumar
Contributor
July 22, 2020

Hi David, 

 

I am also facing same issue. Can you please help me how did you over come this. 

Currently i have Done and Accepted under done category and I need burndown from

TO DO-> Done . I am not much interested from DONE-> ACCEPTED as i want to get credit for the TO DO -> Done for my Team. 

 

Any information provided will be really helpful.

 

Thanks,

Vijay 

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 22, 2020

Burn down is done on the last column on the board.  Status-category and resolution do not matter.  Make sure the status you want to burn-down on are in the last column.

Ideally, those status should also be green (the green status category), and in most cases, I would recommend setting the resolution as you go into one of those status from a status that is open/in-progress, and clearing it if you go back. 

I don't think that's quite right for David's case, but for most of us it is.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events