Jira is among the most-used platforms for software development teams today. It is a great organizational tool that teams rely upon to track tasks, issues, stories, and epics in product and sprint backlogs. 

But Jira can also enable you to boost your development team’s velocity and plan your iterations more accurately. 

In this post, we’re going to look at a powerful, yet often overlooked, feature in Jira: reports. We’ll also look at how Jira reports don’t provide you with all the context you need and how LinearB solves this problem.

Table of Contents

What Are “Reports” in Jira?

In a nutshell, reports in Jira are visual representations of data that is generated by using Jira. A report includes one or more charts. You can use reports individually, but typically they are used in a Jira dashboard.

By design, Jira software is quite open (they even have their own querying language!) so you have lots of freedom to slice and dice your data. You can create your own Jira custom reports from scratch or leverage any number of integrations available in the Atlassian Marketplace.

With so many options, it can be hard to know where to even start, and even harder to know which ones you should be using. Below is a quick rundown of the most widely-used Jira reports, which you can use to quickly pick out the ones that seem most suited to your needs.

  • Resolution time report: Tells you how long it is taking your team to resolve issues
  • Version workload report: Shows you the WIP for each team member in the current iteration
  • User workload report: Shows you the WIP for an individual team member across iterations
  • Time tracking report: Tells you how much time has been spent on individual issues, how much time is left, and whether you are on track to deliver on time
  • Average age report: Shows the average age of unresolved issues
  • Time since issues report: Shows you how many issues were created/updated/resolved/etc. on each day within a particular date range
  • Epic report: Shows you your progress for a specific epic
  • Cumulative flow diagram: Shows you the amount of work completed over time broken down by type

The 4 Most Valuable Jira Reports

Among all the Jira reports, there are 4 that stand out as the most valuable. Before we look at those, it’s important to note that all Jira reports face a big limitation: They can only leverage Jira data.

This is a problem because it deprives you of context about where your team is spending their time. On the Dev Interrupted podcast, Rukmini Reddy, VP of Engineering at Slack, spoke with LinearB’s Co-founder, Dan Lines, about how context is vital in order to fully understand your team’s capacity and their well-being and to identify the factors holding them back.

By combining data from Jira with data from Git, LinearB opens up entirely new depths of insights. In Jira, you can see that an issue or project is behind schedule or how your team has performed over time. But Jira doesn’t provide you enough context to answer the “why”: Why are we behind schedule? Why aren’t we shipping features more quickly? Why are so many bugs popping up? For that, you need a tool like LinearB.

1. Sprint Report

The sprint report is the most widely-used Jira report, because it contains the sprint burndown chart, which has become a key tool in scrum. 

The sprint burndown chart shows you how much work you’ve completed in a sprint and how much work you have left, which gives you a picture of the sprint’s overall status. At a glance, it answers the question, “How is the sprint going?” 

Beneath the chart, you can look at individual issues. You can see when they were completed and how many story points they were worth. 

However, the sprint report doesn’t tell you what kind of issues your team has completed. The sprint report can tell you that you completed, say, 50 story points, but it won’t tell you whether those points consisted of planned or unplanned work, functional stories or bug fixes. Some people use the “single level group by” report in Jira, but still this isn’t great because it creates a report per issue type.

What you need is one chart that combines all the different issue types. This is exactly what the Investment Profile feature is in LinearB. In one pie chart, you can see exactly where your development resources are going.

2. Created vs. Resolved Issues Report

Dev teams are under constant pressure to deliver more features. But sometimes too much has been asked of the development team and the company is headed for a disaster. The created vs. resolved issues report prevents that. 

By showing you the number of issues that have been created and the number of issues that your team has resolved, you can know whether your team is keeping up, getting ahead, or falling behind. This visibility allows you to stay ahead of any problems, advocate hiring more developers, manage expectations, and avoid overwork and crises. 

But this report faces a big limitation: It doesn’t tell you how much work each developer is taking on. In fact, if the created vs. resolved issues report looks healthy for the whole team, it’s even easier to overlook the possibility that too much has been put on the plate of an individual.

By connecting data from Git branches and commits to Jira data like issues, LinearB can help you manage the workloads of individual developers. We’ll even proactively alert you if a team member has maybe taken on too much Work in Progress (WIP) and is at risk of burning out. 

team health

3. Velocity Report

For each sprint, the velocity chart shows you 2 bars: the number of story points the scrum team committed to and the number they completed. This enables you to see how well you are scoping your sprint goals.

Planning accurately is one of the most important things engineering leaders can do, yet it is one of the hardest. In LinearB’s groundbreaking Engineering Benchmarks Study, we determined just how hard it is. We analyzed almost 2,000 dev teams and found that elite teams (the top 10%) only had a planning accuracy of 80% or higher! Strong teams had a planning accuracy of between 65% and 79%. 

Engineering benchmarks chart
Want to learn more about being an elite engineering team? Check out this blog detailing our engineering benchmarks study and methodology.

When you combine benchmarks with metrics, you can confidently identify areas of improvement and set realistic goals. The rule of thumb we recommend at LinearB is to aim for a one tier improvement (e.g. from “fair” to “strong”) over one quarter.

We even created a whole Team Goals system that enables you to set goals in collaboration with your team. You can then track your progress against those goals and use tools like our WorkerB automation bot to help you achieve them. For example, if your goal is to drive down PR size (a terrific goal to have, by the way!) then you can ask WorkerB to send out a reminder to someone when they create a PR that exceeds the goal the team has set.

Nobody wants to review your huge pull request.
Improve your code quality and developer workflow with smaller pull requests. Get started with your free-forever LinearB account today.

4. Control Chart

The control chart shows you two things: 

  1. Your average cycle time over time
  2. The variance of your cycle time over time

Cycle time is the engineering super-metric. Any issue, any bottleneck, any improvement will be reflected in your cycle time. It answers perhaps the most important question facing engineering leaders and their teams all the time: How fast are we going? 

Knowing the variance of your cycle time from sprint to sprint enables you to plan more accurately and also know that the processes on your dev team are refined and reliable. Large variance means that there is a lot of risk in the code your team is shipping which is leading to unforeseen work. 

LinearB enables you to understand your cycle time far more deeply than the control chart. First, we break down cycle time into its 4 individual components. And in just one click, you can see the cycle times of the individual Git branches that are driving the bottlenecks you see in individual cycle time stages. 

With context like this, you can find solutions to slow cycle times in seconds. 

Cycle time breakdown. Dive into your data.
Get context around cycle time bottlenecks in one click. Diving into your data has never been this easy. Get started with our free-forever account today!

The Bottom Line

Jira is a popular tool for good reason. It’s easy to use and it has the key pieces that enable teams to organize and coordinate their work. In this post, we learned that Jira has charts and reports that can help you go beyond just organizing epics, stories, and issues and start optimizing your processes. But we also learned that even these advanced features have serious limitations. 

With the depth of insights you get with LinearB, you can have full context on your dev team. When you pair our metrics with our tools like the engineering benchmarks, Team Goals, and our WorkerB automation bot, you have a powerful, integrated tool to drive sustained improvement at every level of your team and at every stage of your development process. 

To learn about all the ways LinearB can empower you to deliver on your promises and your team to ship more features faster, set up a demo today

Improve your engineering organization at every level with LinearB
Want to improve your engineering processes at every level? Get started with a LinearB free-forever account today!