ow Now you can test out a new dashboard gadget powered by ActionableAgile! We plan to release many gadgets but have started with one - a Cycle Time Summary gadget.
...
The screen contains the following configurations:
...
Gadget Title | This will be the text that displays as the title of the Gadget. The default text is “ActionableAgile Cycle Time”. | ||
Project, filter, and/or board | Choose the project, filter and/or board you want to grab data from.
| ||
Certainty | What percentile do you want the gadget to use to calculate the cycle time summary? The default is 85%. | ||
Max completion age (in days) | How many days back should the gadget go to grab data for the calculation of cycle time? The default is 90 days. Adding a number can be quite finicky; select the start of the box, add your number and then delete the previous number from the box. | ||
Override |
not yet started statuses | By default we consider work items “not yet started” if the status they are in have a status category of |
To Do (blue). These workflow statuses matching this default query will be shown as selected |
. Remove selected statuses you no longer want by clicking on the x icon in the relevant status. To add additional statuses that signify |
work that has not yet started, click on the down arrow in the form field and select the desired |
workflow |
status |
. | |
Override done statuses | By default we consider work items done if the status they are in have a status category of |
Done (Green). These workflow statuses matching this default query will be shown as selected. |
However, you can edit the statuses the gadget uses to calculate cycle time. Why? Well, status categories are not always properly configured. Sometimes, you might want to calculate cycle time for a different part of the workflow - how long it takes to get items to Release Ready, for instance.
Remove selected statuses you no longer want by clicking on the x icon in the relevant status. To add additional statuses that signify |
done work, click on the down arrow in the form field and select the desired workflow status. |
| Note |
|---|
You will want to make sure that your workflow statuses have status categories set. These status categories are how we determine the default workflow statuses used to identify work that is Not Yet Started or Done. In the override status configuration options, you may see statuses that aren’t relevant to your work items as we have to query for all workflow statuses in your Jira instance and their status categories. |
Finished Configuring? You’ll see that the number of issues matching your query are shown in the bottom left. Once you are happy with your configuration, click
| Status | ||||
|---|---|---|---|---|
|
...
...
.
Understanding the Dashboard View
The Cycle Time Summary dashboard gadget provides a percentile based view of how long it took you to get work done in the past.
85% of items completed in the past 90 days took 14 days or less
Calculating your cycle time with a certain probability lets you communicate a probabilistic forecast for the future (assuming the future you’re forecasting for will roughly resemble the past you’re pulling the data from.)
...
Read more about cycle time and the SLE in our Cycle Time Scatterplot documentation.
Viewing the list of Jira issues in the Issue Filter
...