Datum
Flow & cycle time · Jira

Ask Rovo how long Jira issues spend in each status

Updated November 16, 2026

To ask Rovo how long Jira issues spend in each status, you need two things: Rovo on your site, and a source that actually computes time in status, because Jira doesn’t. Jira logs every status change with a timestamp in the issue history, but it never adds the gaps up per status, so a plain Rovo question gets you a summary of the history, not a number you can trust. The shortcut is Linger, which ships a Linger Time in Status Rovo agent: ask “How long has PROJ-1 been in each status?” and it answers in working hours, on the free plan. Below: what Rovo needs, what it can and can’t do natively, and the exact questions to ask.

What is Rovo, and does your site have it?

Rovo is Atlassian’s AI assistant inside Jira and Confluence. You open Chat in the navigation bar, ask in plain language, and Rovo searches and reads the work you have access to. Apps from the Marketplace can add their own agents to Rovo, each with actions that fetch real data from the app.

Atlassian includes Rovo credits in all paid Jira and Confluence Cloud subscriptions: Standard, Premium and Enterprise (Atlassian: How Rovo credits work). Free plans don’t include it. Each chat uses credits from your plan’s monthly allowance. If you don’t see Chat in the top bar, ask your site admin whether Rovo is turned on.

Can Rovo calculate time in status on its own?

No, not as a dependable figure. Rovo answers from what Jira stores, and Jira stores transitions, not durations:

  • Per issue, the History tab shows “To Do → In Progress, 3 Nov 10:14”. The time in each status is the gap between two of those lines, which nobody has computed.
  • Across issues, there’s no field or report Rovo can read that says “In Review: 2.4 days on average”. Jira’s control chart shows cycle time on a board, but not per-status totals Rovo can query.
  • Working time (skipping nights, weekends and holidays) isn’t in Jira at all.

So an AI reading the raw history might estimate, but you can’t check how it got there. The reliable pattern is an agent that calls a calculator and reports its result. If you’d rather do the arithmetic yourself, how to see time in status in Jira walks through the manual method.

How to ask Rovo for time in status with Linger

Linger computes time per status from the changelog, in working hours on your team’s calendar, and exposes it to Rovo through the Linger Time in Status agent.

  1. Install Linger from the Atlassian Marketplace. The agent is part of every plan, including free. A Jira admin can set the working calendar on Apps → Linger Reports → Edit calendar; until then Linger counts Mon–Fri, 09:00–17:00 UTC.
  2. Open the agent. Open Chat in the Jira navigation bar, choose Agents and search for Linger Time in Status (Atlassian: Browse Rovo agents). You can also just ask Rovo chat the question.
  3. Ask your question. The agent picks the right action:
You ask What you get
“How long has PROJ-1 been in each status?” Working time per status for that issue
“What’s our P85 cycle time for project PROJ?” P50 / P85 / P90 per status for the JQL Rovo writes from your words
“How long do issues sit in In Review in PROJ?” The same report, focused on one status
“Which issues are stuck?” Issues past their target, oldest first; give a scope or a number of working days to narrow it
  1. Check the figure. The numbers are the same as Linger’s issue panel and Reports page. Open the issue’s Linger — Time in Status panel and click Show every transition to see the entries and exits behind any figure.

A few honest limits. The agent only reads, and it only includes issues you can see in Jira. Times are working time under the site calendar (or a project’s own calendar, if one is set). Free reports in chat cover up to 1,000 issues; the Standard plan reads up to 5,000. When a result is capped or partial, the agent says so.

What should you ask first?

Start with the question your stand-up keeps circling:

  • “Which status is our bottleneck in PROJ?” The P85 per status shows where work waits longest. Compare it with how to find bottlenecks in Jira.
  • “Which issues are stuck in PROJ for more than 5 working days?” A list you can act on today.
  • “What’s our P85 cycle time for issues resolved last month?” One number you can track. For what it measures, see how to measure cycle time in Jira.

Rovo writes the JQL from your words, so name the project key and the status the way they appear in Jira.

When should you use the reports page instead?

Chat is fastest for a quick question. Open Apps → Linger Reports when you want to see the shape of the data:

  • Charts on the Statuses tab: average or P85 working time per status, and a stacked bar of time per status for the 10 slowest issues. Both are free.
  • Cycle-time trend (Standard): P50 and P85 per week or month of completion.
  • CSV download, saved reports and the Linger — Flow Report dashboard gadget.

Linger’s screens are available in English, German, French and Spanish and follow each person’s Jira language; Rovo answers stay in English.

The takeaway

Rovo is only as good as what it can read, and Jira doesn’t store time in status. Give Rovo a source that computes it, and “how long has this been in review?” becomes a one-line question with a checkable answer. Linger adds that agent on the free plan; if you’re still comparing options, see the dedicated time-in-status apps for Jira.

Frequently asked questions

Can Rovo tell me how long an issue was in each status?
Not reliably on its own. Jira records each status change in the issue history but never adds up the time per status, so Rovo has no figure to read. With a time-in-status app that ships a Rovo agent, such as Linger, Rovo calls the app and returns the computed working time per status.
Which Atlassian plans include Rovo?
Atlassian includes Rovo credits in paid Jira and Confluence Cloud plans (Standard, Premium and Enterprise). Free plans don't include it. Check with your site admin whether Rovo is turned on for your site.
Does the Linger agent cost extra?
No. The Linger Time in Status agent comes with the app, including the free plan. Free reports in chat cover up to 1,000 issues; the Standard plan reads up to 5,000. Rovo chats themselves use your site's Rovo credits. Teams of up to 10 users get Standard free too, and larger teams get a 30-day trial.
Will the agent show issues I can't see?
No. Answers only include issues you can already browse in Jira.
Is there an app that answers time in status questions in Rovo?
Yes. Linger adds the Linger Time in Status agent. Ask it how long an issue has been in each status, the P50, P85 or P90 time per status for any JQL, or which issues are stuck or over target.

← All Datum guides