Dashboard Gallery

Jira dashboards

These Jira dashboards give a clear overview of your Jira instance and provide more details on the key items over which the engineering team needs oversight, like build status, critical bugs, and costs.

Bruce Cullen, SquaredUp

Jira dashboard for engineering management team

Challenge

Teams using Jira need to track bugs to know where there are defect clusters, how many bugs are being raised vs. closed, and whether there are any critical bugs. You also want to track the status of your builds and how robust they are. Plus, you want to stick to the budget for Azure infrastructure costs, for example.

Although Jira has a native dashboarding capability, the dashboards are only as good as the Jira data and, as an engineering team, you need to be able to see data from more sources than Jira. Plus, Jira doesn’t provide a way to create metrics and dashboards showing the detail you need while also rolling up the statuses of KPIs to centralized project management or release teams.

There needs to be a centralised place to roll up all the data from across the teams and use cases to get a unified view.

Solution

By using the Jira plugin to create Jira dashboards in SquaredUp, the Engineering Team can create their own dashboards and display all the metrics they need, from bug severity to the status of build runs. At the same time, they can roll up KPIs using the KPI feature and red-amber-green (RAG) status tile for health status so management can get an overview of performance at a glance.

Creating Jira dashboards in SquaredUp means Engineering Management doesn’t have the additional work of collating all the detailed Jira data to make sense of it from a high level. It also enables Release Teams to more easily consume data surfaced from all the engineering teams, while still being able to drill into the details of each dashboard as needed.

Dashboard walkthrough

Setting up a Jira dashboard in SquaredUp is simple. You just need to provide the URL for your Jira cloud instance, a name, username, and an API token.

Management dashboard

The first Jira dashboard lets the Engineering Management team get a fast overview of bugs, Azure cost data, and DevOps build information for build jobs. This dashboard was created by inputting JQL directly into the SquaredUp dashboard.

Here’s a breakdown of what the above dashboard shows.

Monitoring and taking action on bugs with Jira data:

In the top left you can see the number of open bugs. This is labelled as a KPI so it can be rolled up to bigger, overarching dashboards where needed.
The donut charts break down the bug backlog and defect clusters. The bug backlog shows the proportion of bug fixing versus engineering work, like Stories. The defect clusters help identify where the bugs are occurring so you know where to focus time.
Just below that, on the left, is a table showing bug severity, with security critical and globalization bugs being flagged just to the right of the donuts.
The bottom left shows a line graph of bugs raised trend.
The larger table across the middle shows Jira high priority bugs for immediate action.

Azure infrastructure cost monitoring:

On the right near the top is a 30-day cost figure to show whether the cost of Azure infrastructure usage (where the test resources live) is within the department’s agreed budget.

Azure DevOps build information:

At the top right is a roll-up of the statuses of the build runs in play to give a high-level overview of where each build is at and whether a build has failed.

Team dashboards

These next three dashboards are the more detailed, team-level dashboards.

The first is the story dashboard that provides oversight of the story by component, the stories in progress, including the backlog and the number closed by both quarter and in the current year. There is also a tracker for the epics in progress, the backlog, and the number closed.

The Jira dashboard for bugs gives greater detail into the details of the critical bugs, the open bugs by component, the bug raise and close rates, and the number of bugs by priority.

Finally, there is also the release overview Jira dashboard that provides insights into the progress status of each release, the stories and epics that have been recently started, as well as the epics and bugs by priority.

Get the dashboard

You can build these Jira dashboards in SquaredUp in minutes. Here's how to get started for free:

Create a free SquaredUp account.
Add the Jira data source.

To see what other dashboards you can create, including Azure dashboards, check out our Dashboard Gallery.

Get SquaredUp free

Read more from our blog

Jira Automation Demystified

Repetitive tasks can be time consuming. In an ideal world, automation would remove all of the grunt work when it comes to solving business problems, freeing us up to execute on more strategic decisions. Luckily, Jira has the capabilities to take a load of tasks off your hands – including tracking your issues, posts, features,...

How to build the ideal dev team dashboard

Slack is great for communicating changes and events across a development team, but what’s missing is that ‘snapshot’ of the current state of play. Sure, you can switch between tabs for Jira, GitHub, your CI/CD tool and monitoring tools, but a dashboard that brings this all together makes it much easier for the whole team...

5 Azure DevOps Hacks: February Community Round-up

Catch up on the latest SquaredUp Community news, including topics like PowerShell and Azure Monitor.

Build a CircleCI Dashboard to visualize all your CI/CD data

CircleCI’s powerful features help dev teams automate and accelerate their build pipelines—while also allowing the flexibility that engineering teams need to build, test, and ship code across environments and tool stacks. But with scale comes complexity—tracking and observing your CircleCI pipelines and workflows across different teams throughout your organization will become increasingly challenging as you grow. ...

Dashboard Gallery

Jira dashboards

Challenge

Solution