Ask Rovo Where Your Jira Time Goes

[#1]

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 number — it can analyze a metric across many issues and tell you where the time went, what stands out, and what to check next. This article walks through what each side does, and how they speed up your workflow when combined.

What Time Metrics Tracker does

Time Metrics Tracker measures how long issues spend between statuses or in specific workflow stages, using the transition history Jira already records. With it, teams can:

• Track Cycle Time, Lead Time, Resolution Time, Time in Status, and custom metrics between any two statuses.
• Exclude statuses that shouldn't count (like Waiting for Customer) and apply a work schedule so times reflect business hours.
• Set Warning and Critical limits so a metric flags itself when work runs long.
• Monitor everything through reports, dashboard gadgets, and Flow Insights — no spreadsheet exports.

In short: the app calculates trustworthy time metrics from your real workflow. That's the foundation the agent builds on.

What the Rovo Agent does

The agent lets you get to those metrics by asking, instead of navigating the app. It can:

• List your configured metrics — a quick way to see what's set up in your instance.
• Check a single issue — "How much time has INTD-123 spent according to Cycle Time?"
• Analyze a whole set of issues — calculate a metric across a project and period, and read the results for you.

That last ability is what changed. Ask "Which issues have the highest Cycle Time created this week in the MARC project?" and the agent replies in three layers: a short summary, a results table (each issue with its metric, time, and current status), and an insights read-out with observations and recommended actions.

The speed-up is the point. Answering that question by hand usually means exporting issue history, building a pivot, sorting by time, and working out which status ate the most. The agent does that reading in the time it takes to type the question — and hands back not just data, but what it means.

Better together: the synergy

The app and the agent play different roles, and that's exactly why they work well as a pair. Time Metrics Tracker calculates the metrics; the Rovo Agent interprets them. One gives you accurate numbers grounded in your workflow; the other turns those numbers into a next step.

Here's the agent answering a real question about Cycle Time:

 

Example output. Actual issues, times, and observations depend on your workflow, metric configuration, and data.

Notice what it surfaces automatically — the same things an experienced analyst would look for:

• Context that explains the numbers. The issues were all created this week, so the agent notes their Cycle Times are naturally low — a heads-up not to misread small numbers as a problem.
• Cycle Time vs. Lead Time. For several issues the Lead Time is much higher than the Cycle Time, meaning they sat in the backlog or To Do before work began. That points at the queue, not the active work — a distinction that's easy to miss from one number.
• Timers still running. Every issue is still In progress, so the agent flags that these times will keep climbing until they reach a stop status. Live, not final.
• Artifacts and clusters. It calls out issues sitting at 0m (created, but work hasn't started) and two issues with near-identical times (possibly related tasks picked up in parallel) — patterns to understand, not read as a trend.

Then it turns that into recommended actions: because it knows your Warning and Critical limits, it points out issues already sitting in Critical for Lead Time even though they were created this week, suggests reviewing whether those thresholds are set too tight, and prompts you to verify the start status on any 0m issues where work has actually begun. It's a fast first pass, not a verdict — the full detail stays in the app's reports, gadgets, and Flow Insights for when you want to dig deeper.

The result: the app makes the metrics reliable, and the agent makes them fast to act on. Together they take you from "the number moved" to "here's where, and here's what to do" without leaving Jira.

How to find the agent

To open the Time Metrics Tracker Rovo Agent:

1. Open Jira.
2. Click Ask Rovo.
3. Go to Agents or View all agents.
4. Search for the Time Metrics Tracker agent.
5. Open the agent and enter your question.

 

Try it on your own data

Ask the agent about a metric you care about:

• Which issues have the highest Cycle Time created this week in [PROJECT]?
• Analyze Resolution Time for [PROJECT] this month and tell me what stands out.
• Show the same results in business days.

Name a metric you've configured (or ask the agent to list them first), and keep the scope focused — it reads a sample of up to 250 issues per request, so a project and a time window work best.

Time Metrics Tracker gives you the metrics you can trust; the Rovo Agent tells you where your Jira time goes — and what to do about it.

Try Time Metrics Tracker on the Marketplace