...
The In Progress Statuses option allows you to customize which statuses are considered "In Progress" for all your charts, whether it's Cycle Time Histogram, Time in Status Cycle Time, or Cycle Time Trend Charts. This flexibility lets you redefine what "In Progress" means for your workflow by including statuses that are typically categorized as "To Do" or "Done".
By default, all statuses of the “In Progress” status category are predefined.
Sometimes, your team might have specific statuses that don’t fit neatly into the default "In Progress" category but are crucial to your workflow. For example, you might have a "To Do" status like "Design Approved" or a "Done" status like "Ready for Release". By selecting these as "In Progress," you can ensure that the time spent in these critical stages is accurately tracked and analyzed.
The “In Progress” Statuses option allows you to tailor your charts to reflect the unique aspects of your workflow, ensuring that no crucial stage is overlooked, regardless of how it's categorized in Jira.
...
The Done Statuses option allows you to customize which statuses are considered "Done" for the Cycle Time Histogram and Cycle Time Trend Charts. This flexibility lets you redefine what "Done" means for your workflow by including statuses that are typically categorized as "In Progress" or even "To Do".
By default, all statuses of the “Done” status category are predefined.
In some workflows, the completion point might not align with the traditional "Done" category. For example, your team might have an "In Progress" status like "Ready for Release" or a "To Do" status like "Final Review" that marks the end of their process. By selecting these statuses as "Done", you can ensure that your charts accurately reflect when work is truly finished.
Exception: the Done Statuses option is not available for the Time in Status Cycle Time Chart because this chart’s primary focus is to track how long tasks are spent in each individual status - no matter their category, rather than when they are completed. The Time in Status Cycle Time Chart aims to provide insights into the time distribution across all statuses within the workflow, making the concept of a "Done" status unnecessary for this specific analysis.
...
First transition to status: starts or pauses the timer the first time the issue transitions to a selected status. This option is a default for the “Start timer on” field, meaning the timer starts when an issue first enters an “In Progress” status.
Last transition to status: starts or pauses the timer the last time the issue transitions to a selected status. This option is the default for the ”Pause timer on” field, meaning the timer stops when an issue last enters a “Done” status.
First transition from status: starts or pauses the timer the first time the issue transitions from a selected status.
Last transition from status: starts or pauses the timer the last time the issue transitions from a selected status.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
The Timer is available only for one status. If the “In Progress” or the “Done” status category includes a few statuses and you did not clarify which one status you want to track exactly, all “Timer” options are blocked. |
There are a few scenarios to help identify what this setting is about.
Managing reopened issues.
Imagine an issue that gets reopened several times during a sprint. By using the Start timer on: First transition to status and the Pause timer on: Last transition to status, you ensure that the timer only tracks the time from the first moment the issue starts progressing to the final moment it is marked as Done, giving you an accurate measure of the total active work time.Tracking revisions in review:
Consider an issue that bounces back and forth between "In Progress" and "Review" multiple times. Setting Start timer on: Last transition from status and Pause timer on: First transition to status allows you to focus on the time spent in the final round of work before it was last sent for review, ensuring you capture the most critical work phase.Focus on the final push:
Suppose you’re interested in how long it takes to complete the final phase of work on an issue. In that case, you might set Start timer on: Last transition from one “Done” status (for example, "Ready for Release") and Pause timer on: Last transition to another final “Done” status (for example, "Released"). This setup tracks only the last, decisive push to move the issue from being ready to actually being released, giving you a clear view of the final effort required to get the issue over the finish line.
...