Get started with Atlassian Analytics
Learn how to add Atlassian Analytics to a site and understand what you need to query data and create charts.
"Cross-team DevOps effectiveness scorecard" template
This dashboard template is only available for Atlassian Data Lake connections that include Jira data and have scope of data set to “All”. Read more about how to connect to the Atlassian Data Lake.
This dashboard displays a set of key scorecards that help to highlight common problem areas across your department by using the data from your development tooling. In this dashboard, we determine a department as the teams working on projects of the same category, which is based on the “Dropdown” control labeled Project category.
Controls on the dashboard
Use the following controls to configure the dashboard:
Current date interval | “Calendar” control to filter charts to display data relating to issues completed during the selected date range. |
|---|---|
Date bucket | “Dropdown” control to group data by week, month, quarter, or year. |
Project category | “Dropdown” controls to specify the departments that this dashboard should focus on. If you reset this control, the charts will look at issues across all project categories. |
Issue types to consider | “Dropdown” control to select specific issue types that you want this dashboard to consider. If you reset this control, the charts will look at issues of all types. |
Issue labels to ignore | “Dropdown” control to select specific issue types that you want this dashboard to ignore. If you reset this control, the charts will look at all issues with any label. |
Issue types to configure as bugs | “Dropdown” control to select specific issue types that you want this dashboard to consider as bugs. If you reset this control, the charts will look at issues of all types. |
Mapping categories of work
Mapping issues into categories of work helps teams keep track of and prioritize the effort spent in each category. At Atlassian, we bucket the work (in other words, Jira issues) into four categories: Run the business, Change the business, Developer productivity, and Team management.
To map the work categories:
Use the “Text input” controls to specify the names of the categories of work.
Use the “Dropdown” controls to specify the Jira issue labels that map to each category of work.
Note the following:
If an issue maps to multiple labels, the charts will map the issue to the first label match in the list.
The first category of work (default is “Run the business”) in this mapping is also used as the target goal in some charts, as we believe teams should spend less than 10% of their time working on this category.
Mapping statuses of work in review
Specify which issue statuses indicate “In review”. This mapping ensures that the “Teams with issues spent less than 50% of time reviewing work” and “Time spent in ‘In review’ status” charts properly display the proportion of time spent on work in review.
Charts on the dashboard
Quick overview
The quick overview gives a holistic view of your engineering health over the last four weeks, helping you see where your strengths and weaknesses are. The trends beside the number indicate the movement of the metrics in last four weeks.
Median issue cycle time
The median number of days it took for issues to move from “To do” to “Done” in the last four weeks.
Issues completed
The number of issues completed in the last four weeks.
Deployment frequency
The average number of production deployments in the last four weeks.
Bugs raised
The number of bugs opened in the last four weeks.
Speed of delivery
Teams with issue cycle time over or under 7 days
Issue cycle time looks at the total time an issue spends “In progress”. Assess the workflows of your teams by seeing how many teams are meeting or missing the target cycle time each month.
Supporting metrics for cycle time
Shows the median development, issue, and PR cycle times side by side for easy comparison and analysis.
Cycle time per team
A listing of all projects, the number of issues worked on, and their median cycle times each month.
Teams deploying at least four times a month
Deployment frequency counts the number of times a change gets deployed to production. Assess the spread of teams meeting or missing the target of at least four deployments per month.
Supporting metrics for deployment frequency breakdown
A quick overview of deployment success rate, median deployment time, and maximum deployment time to quickly isolate the outlier services.
Deployments per team
A listing of all projects and the number of deployments during the selected date interval.
Work breakdown
Development time breakdown
A breakdown view of the time spent by the teams in each development category. Use this chart to identify anomalies in the spread of time.
Activity breakdown per team
A listing of all projects and their time spent in each development category.
Teams that spent less than 50% of time reviewing work
The number of teams that are meeting or missing the target for the amount of time spent reviewing issues. Teams that spend too much time “In review” may need to improve their review process.
Time spent in “In review” status
A listing of all projects, the number of issues worked on, and the percentage of time spent reviewing issues during the selected date interval.
Teams that spent less than 10% of time to run the business
The number of teams that are spending the appropriate amount of time working on “Run the business” issues.
Time spent to run the business
A listing of all projects, the number of issues categorized as “Run the business”, and how much time was spent working on these issues each month.
Bottlenecks
Teams that have at most 10% overloaded assignees
The number of teams that have more or less than 10% of team members with more than three concurrent issues in progress.
Supporting metrics
Provide a percentage distribution of issues that needs attention — categorized as “Blocked issues”, “Handed over issues”, and “Stuck issues”.
Work in progress per team
A listing of all projects and the percentage of overloaded assignees in the team.
Quality
Issues opened vs. bugs raised
The number of bugs raised compared to the number of non-bugs being worked on.
Supporting metrics
Get deeper stats on the bugs by looking at the number of bugs, the number of critical bugs, and the percentage of issues raised as bugs.
Total number of bugs raised per team
A listing of all projects with the number of bugs raised and the number of critical bugs against each project.
Mean time to resolution
The average time it takes to close the bugs.
Supporting metrics
Breakdown of resolution time per bug priority.
Mean time to resolution per team
A listing of all projects with the number of bugs resolved and their median resolution time.
Was this helpful?
Still need help?
The Atlassian Community is here for you.