Vanta Logo
SPONSOR
Automate SOC 2 & ISO 27001 compliance with Vanta. Get $1,000 off.
Up to date
Published
4 min read

Trevor I. Lasn

Staff Software Engineer, Engineering Manager

Become a Better Engineering Manager with JQL

Using Jira queries to understand engineering trends and drive improvements

If you use Jira to manage engineering work, JQL queries can provide clear visibility into work patterns and output across different projects. These queries offer precise data about completed work, helping inform decisions about resource allocation and process improvements.

Engineering work is messy. Individual tickets tell small stories, but the big picture often stays hidden. Teams might feel productive day-to-day while technical debt silently grows. A project might seem on track until you notice one team spending most of their time fixing bugs instead of building features. These patterns emerge when you look at the data over time.

Time reveals truth in engineering. A month of data might look great - lots of completed tickets, features shipping on schedule. But zoom out to six months and you might spot concerning trends: rising bug counts, slower delivery times, growing backlogs of technical debt. A year of data shows you seasonal ebbs and flows. Two years expose deeper patterns about how your engineering organization really works.

This view of the bigger picture changes how you think about engineering effectiveness. Instead of reacting to the latest fire, you can spot smoke before it becomes a blaze. You start asking better questions: Why does our velocity drop every winter? How come this team’s bug count keeps climbing? Are our recent process changes actually helping? The answers often hide in plain sight - in your project data.

Finding patterns in your project data is surprisingly straightforward with JQL. Here’s a sample query I use to get an annual overview of our work:

Let’s break this down. We’re looking at tickets from the Mobile App project, excluding the Platform team’s work. The date range covers all of 2024 - anything that was marked as done during that year.

This query gives you every resolved ticket for 2024. From here, you can dig deeper. Want to see how many were bugs? Add AND type = Bug — Curious about feature work? Change it to type = Feature

How many bugs did the Mobile App team resolve in 2024?


How many features did the Mobile App team deliver in 2024?


Tip: You can export the output as CSV and use a spreadsheet tool to visualize the data. This makes it easier to spot trends and patterns.

The value of these queries becomes crystal clear in leadership discussions. When asked “How are the teams doing?” or “Are we improving?”, you can respond with concrete data instead of gut feelings. You can show that bug counts dropped 30% after implementing automated testing, or that the team delivered 40% more features while maintaining quality. This data backs up your decisions and helps justify future improvements.

These insights also make you more effective as a leader. Spotting a rising bug count early lets you address issues before they impact delivery. Seeing that one team handles twice the bugs of others might highlight a need for more testing resources. Having this data doesn’t just help you answer questions - it helps you drive meaningful improvements across your engineering organization.

If you found this article helpful, you might enjoy my free newsletter. I share developer tips and insights to help you grow your skills and career.


More Articles You Might Enjoy

If you enjoyed this article, you might find these related pieces interesting as well. If you like what I have to say, please check out the sponsors who are supporting me. Much appreciated!

Leadership
4 min read

Make It Work First Before Optimizing

Users don't care how elegant your code is. They care if it solves their problem.

Sep 27, 2024
Read article
Leadership
4 min read

Weeks of Coding Can Save You Hours of Planning

Weeks of coding can save you hours of planning. It’s one of those sayings that’s been around forever, and for good reason—it’s a warning that still holds up today.

Sep 21, 2024
Read article
Leadership
5 min read

Outdated Docs Are Tech Debt

Teams often neglect to create good documentation. Code gets delivered, but updating the docs is treated as a secondary task, easily postponed—until it’s too late.

Sep 22, 2024
Read article
Leadership
4 min read

Write Documentation Like a Journalist

Create comprehensive, engaging documentation by adopting journalistic techniques for research and storytelling

Sep 26, 2024
Read article
Leadership
3 min read

Internal Mobility

Just like a utility player on a sports team discovering their ideal position, internal mobility allows you to explore different areas of engineering and find your true passion.

Sep 23, 2024
Read article
Leadership
5 min read

Advice to New Engineering Managers

Tips for being an effective engineering leader and how to avoid common pitfalls

Feb 15, 2025
Read article
Leadership
3 min read

Engineering Managers Should Write Code

Engineering managers who stop writing code lose touch with their teams and become ineffective leaders

Sep 18, 2024
Read article
Leadership
3 min read

The 5:1 Rule: Effective Performance Reviews For High-Performing Teams

Research reveals the ideal ratio of positive to negative feedback within high performing teams

Mar 20, 2025
Read article
Leadership
5 min read

A Company Is Not a Family. It's a Sports Team

'We're not just a company, we're a family!' It's a nice sentiment, sure. But it's also a load of crap.

Oct 5, 2024
Read article

Become a better engineer

Here are engineering resources I've personally vetted and use. They focus on skills you'll actually need to build and scale real projects - the kind of experience that gets you hired or promoted.

Many companies have a fixed annual stipend per engineer (e.g. $2,000) for use towards learning resources. If your company offers this stipend, you can forward them your invoices directly for reimbursement. By using my affiliate links, you support my work and get a discount at the same!


This article was originally published on https://www.trevorlasn.com/blog/jql-for-engineering-metrics-and-trends. It was written by a human and polished using grammar tools for clarity.