Hello! We are on Jira Cloud and most of our projects are Scrum. Typical workflow looks like this Backlog > Dev Ready > Dev In Progress > Integration > QA > Beta > Prod > Closed Statuses in a done state are QA, Beta, Prod, and Closed. Only Closed state sets the resolution. QA, Beta, and Prod are environments. Not all issues reach Closed status in the same sprint. I understand the last column on the board will drive the Sprint Report. Few questions * What would be the best way to report progress / work completed in the Sprint if only QA was completed? * What would be the best way to report progress / work completed in the Sprint for each environment? * If the last column has QA, Beta, Prod, and Closed statuses, can we keep the tickets in Beta and Prod statuses open, and move them to future sprints until they are closed? Please point out best practices and suggest better/different ways of reporting as tickets move through different environments. Best, Dharmesh

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

Reporting on multiple done states

Dharmesh Barot

Hello!

We are on Jira Cloud and most of our projects are Scrum.

Typical workflow looks like this

Backlog > Dev Ready > Dev In Progress > Integration > QA > Beta > Prod > Closed

Statuses in a done state are QA, Beta, Prod, and Closed. Only Closed state sets the resolution. QA, Beta, and Prod are environments.

Not all issues reach Closed status in the same sprint.

I understand the last column on the board will drive the Sprint Report.

Few questions

What would be the best way to report progress / work completed in the Sprint if only QA was completed?
What would be the best way to report progress / work completed in the Sprint for each environment?
If the last column has QA, Beta, Prod, and Closed statuses, can we keep the tickets in Beta and Prod statuses open, and move them to future sprints until they are closed?

Please point out best practices and suggest better/different ways of reporting as tickets move through different environments.

Best,

Dharmesh

Accepted answers

Bill Sheboy

Hi @Dharmesh Barot

What is the problem you are trying to solve by reporting "progress / work completed"?

Your team is using a scrum board, and the workflow you describe indicates work does not always finish within the boundaries of a sprint. Is that correct?

If so, please consider whether or not the scrum framework is a good fit for the way the team currently works, or if there are improvements which could allow work to finish within a sprint. Given the current use of status values (your workflow) the current built-in scrum reports may not be as helpful as you wish. Instead consider creating a simple dashboard which shows how you want to make progress visible. For example, summarizing your building, validation, and releasing status values.

Best regards,

Bill

All comments

Nic Brough -Adaptavist-

Start by defining what is "done". Is it done when it goes into QA, or after it passes for example? Once you have a clear definition of done, related to status, you can put all the "done" status in the last column, and your sprint reports will give you the reports.
Probably by filtering for "current sprint" and "done" and then running that filter through dashboard gadgets
No, the column means "done", so issues in there will not move to future sprints, as they're done.

Bill Sheboy

Hi @Dharmesh Barot

What is the problem you are trying to solve by reporting "progress / work completed"?

Your team is using a scrum board, and the workflow you describe indicates work does not always finish within the boundaries of a sprint. Is that correct?

Best regards,

Bill

Dharmesh Barot

@Bill Sheboy We are exactly at this cross-roads whether Scrum is the right fit.

The problem we are trying to solve is to track and visualize what initial development work is getting done, and plan resources for remaining initial dev work.

There may be work to be done as tickets move to different environments.

Currently reports are not useful because we can't accurately report on dev work completed in a Sprint.

Appreciate your response.

Bill Sheboy

Got it, and thanks for explaining! You could try to create some specific filters to see what happened during the sprint timeframes. For example:

project = myProject<br> AND status CHANGED FROM "Dev In Progress" TO "Integration"<br>&nbsp;DURING&nbsp;(myStartSprintDate,&nbsp;myEndSprintDate)<br>&nbsp;ORDER BY Key

This would show which issues completed development during your sprint timeframe.

To see more JQL syntax like this, please see this documentation:

https://support.atlassian.com/jira-core-cloud/docs/advanced-search-reference-jql-operators/

Dharmesh Barot

Thanks @Bill Sheboy

I will give it a try.

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