Anastasiia Maliei SaaSJet Atlassian Partner

Turning Jira Sprint Metrics into a Retrospective Brief with Rovo The sprint ended yesterday. The retrospective starts in 15 minutes. The Sprint Report is full of charts. Velocity went down. Scope went up. Completion rate improved. Bugs dropped by more than half. And somewhere in the middle of the sprint, 52 story points…

Financial managers, CFOs, and controllers are constantly balancing two challenges: maintaining financial transparency and ensuring that projects don’t exceed budgets. In fast-moving organizations, relying on spreadsheets and late reporting is not enough. By the time overruns are noticed, it’s often too late to fix them.…

Every team hits this wall sooner or later. You’ve got a solid "Time in Status" report that actually gives you the real picture—bottlenecks, wait times, and whether your delivery is speeding up or dragging. The catch? Your weekly updates live in Confluence. Your retros happen there, too. Same goes for stakeholder summaries…

How a healthcare content team can turn Jira status history into useful review-and-approval metrics Most articles about flow metrics use software examples: code review, deployment, cycle time. But review-heavy teams outside software can benefit from the same approach. Consider a clinical content team working with regulated,…

Closing hundreds of tickets every month sounds productive. But it doesn't necessarily tell you whether your support process is actually getting better. The problem usually isn't a lack of data. Jira is already collecting plenty of it. The harder part is figuring out which numbers are actually useful. For most support…

Product teams using Jira Product Discovery are usually great at prioritization. Ideas are scored by impact, effort, confidence, reach, customer feedback, and business value. Roadmaps become more objective, discussions become more structured, and prioritization decisions are easier to justify. But there is one dimension…

If you track Cycle Time, Lead Time, or Resolution Time in Jira, you've almost certainly run into a number that made you stop and double-check your sanity. Picture this: a ticket moves to In Progress on Friday at 5:00 PM and gets marked as Done on Monday at 9:00 AM. Jira's raw issue history logs that as roughly 64 hours.…

Time Metrics Tracker has always turned Jira's status history into the time metrics teams rely on — Cycle Time, Lead Time, Resolution Time, and more. Its Rovo Agent lets you ask about those metrics in plain language, right inside Jira. Now the two work together more closely than ever. The agent no longer just returns a…

When people talk about Kanban metrics, the examples are almost always from software teams — Cycle Time on a dev board, WIP limits on engineering columns, throughput per sprint. But marketing teams run on flow just as much as engineering does, and often with far more handoffs. A single campaign asset usually passes through…

Few topics can make an agile team sigh faster than story points. Is this a 3 or a 5? Should bugs have points? Why did an 8-point story finish faster than a 2-point one? Are we estimating complexity, effort, uncertainty, risk, or all of the above depending on how tired everyone is during refinement? Story points were…

At first glance, grant work may look like a set of documents: an application, a budget, supporting files, an agreement, and reports. But in reality, it is a process with multiple stages, owners, handoffs, waiting time, and deadlines. And any process can be tracked, measured, and improved. That is why Jira can be a…

If your team needs to understand not only how long work takes, but also where time is spent between statuses, a Time Between Statuses report can give you a much clearer view of workflow delays and bottlenecks. Jira stores issue history and status changes, but turning that data into a practical time report is not always…

Jira already captures a lot of workflow history: when an issue changes status, who works on it, when it is completed, and how long it stays in different parts of the process. But when a delivery metric starts getting worse, teams often need more than a list of issues or a single average value. They need to understand what…

Hi Community, I’m curious how different teams analyze where time is actually spent in their Jira workflows. Many teams track metrics like Cycle Time, Lead Time, Resolution Time, or time in specific statuses such as Code Review, QA, Waiting for Customer, or Blocked. But one challenge I often see is that a single number does…

Your Jira board can show that work is In Progress. But it does not always show whether that work is actually moving. For engineering and delivery teams, this is where Jira conversations often get difficult: “Why is release taking longer?” “Where exactly are we losing time?” “Is the issue in development, review, QA,…

Every team has workflow data in Jira. Status changes, transitions, timestamps — it’s all there. The problem is turning that data into a useful picture during an actual review. Not after an hour of exporting. Not with a spreadsheet someone built last quarter. But right now, in context, when the question comes up. That’s the…

SLAs are supposed to make service delivery predictable. They tell teams what “on time” means, help stakeholders understand expectations, and give managers a clear way to track performance. But when an SLA starts breaking, the real question is rarely just: “Did we miss the target?” The more useful question is: “Where…

Grant application workflows are rarely simple. A single application can move through eligibility checks, compliance review, expert evaluation, committee decision, approval, funding, and post-award monitoring. Each step may involve different departments, reviewers, legal requirements, and deadlines. That is why many…

See where your tracked time actually goes Cycle Time is often the first metric teams check when delivery starts to slow down. It answers an important question: How long does it take work to move through our process? But once you see that Cycle Time is growing, the next question is usually harder: Where is that time…

Most teams don’t suddenly “become slow.” More often, delivery performance changes quietly. One week QA takes a little longer. Then a few stories miss the release window. Then the team starts hearing the classic sentence: “It feels like everything is stuck in testing.” Feels like is a dangerous metric. It creates opinions,…

When did your delivery start slowing down? For many Jira teams, this is a surprisingly hard question to answer. A sprint slips. A release takes longer than expected. A few issues suddenly stay “In Progress” far beyond what feels normal. But when you look at your basic metrics, nothing stands out. The main number looks…

A single metric value tells you where you are. A trend tells you where you're heading — and what to do about it. Why one number is never the full story Most teams check a workflow metric the same way: open a report, look at the current Cycle Time or Code Review time, nod, and move on. The number looks fine. Or it doesn't.…

If you use Kanban in Jira, Cycle Time is probably one of the first metrics you look at. And that makes sense: it helps you understand how long work takes once it has started. But Cycle Time alone does not tell the whole story. Two teams can have the same average Cycle Time and still work very differently. One may deliver…

If you’ve ever tried to find out in Jira how much time an issue actually spent between statuses, you probably started with JQL — and quickly ran into its limitations. JQL is great for searching issues by status, date, assignee, or change history. But when it comes to time in status, cycle time, lead time, or the actual…

Approval time is one of the easiest workflow metrics to overlook in Jira — and one of the most expensive to ignore. A task can move quickly through execution, testing, or delivery, but still get stuck waiting for approval from a manager, reviewer, legal team, procurement, compliance, or another stakeholder. When that…

If you’re an Engineering Manager, Delivery Manager in a software product team, you’ve probably seen this argument before: “Delivery slowed down because the review took too long.” “No, QA became the bottleneck.” “Actually, dev finished on time — the handoff broke.” The problem is that Jira workflows show where work is now,…

When a deadline slips, the conversation often turns emotional fast: “You said it would be done last week.” “We’ve been waiting on your team.” “No, we replied — your side didn’t move.” If you’ve ever delivered work through a client (approvals, reviews, access, sign-offs), you know the uncomfortable truth: a big part of…

Bottlenecks rarely appear “out of nowhere.” In most Jira workflows, the warning signs are visible days (or weeks) before teams feel the full pain: missed sprint goals, overloaded reviewers, QA queues, or a “Blocked” column that quietly becomes a parking lot. This article walks through a practical, Jira-native way to spot…

We have all witnessed it. A high-priority project is behind schedule. The stakeholders are getting restless. In a moment of panic, management reaches for the trusty lever: “Hire more developers.” It makes perfect sense. More developers mean more hands on deck. The project will get done faster, right? But weeks later, the…