Time in Status in 2025: stronger foundations, sharper insights, and a big finish

[#1]

If 2025 had one theme for Time in Status, it would be this: build for the future without slowing down the improvements you feel today.

A lot of our work this year happened behind the scenes (the kind of work you don’t always see immediately—but you definitely benefit from long-term). And at the same time, we shipped customer-facing updates that make it easier to understand flow, spot blockers, and communicate progress without turning Jira reporting into a second job.

Here’s our 2025 recap—what we built, why we built it, and how it helps you.

The biggest initiative of the year: migrating Time in Status to Atlassian Forge

Throughout 2025, we’ve been working steadily on migrating Time in Status to Atlassian Forge. This transition is a major step in making the app more secure, more reliable, and more aligned with Atlassian’s long-term Cloud direction.

Quick reminder: what is Atlassian Forge?

Forge is Atlassian’s modern cloud app development platform. Apps built on Forge:

• Run inside Atlassian’s own cloud infrastructure instead of third-party servers
  
  
• Integrate with Jira and Confluence through a secure, sandboxed runtime designed to isolate customer data and limit data egress
  
  
• Can align with Atlassian’s data residency controls, so in-scope app data can stay in specific regions (EU, US, Germany, etc.), similar to Jira Cloud itself
  
  
• Reflect Atlassian’s increasing investment in Forge as the standard platform for new cloud apps and as a key part of their security and trust program
  
  

Why this matters for you

Moving Time in Status to Forge isn’t just a technical refactor—it’s a real customer value upgrade:

• Stronger security & compliance
  Your data stays within Atlassian’s managed cloud instead of external infrastructure, which simplifies security reviews and supports regulatory requirements.
• A better data residency story
  Forge is designed to align app data with Atlassian’s data residency features—critical if your organization must keep data in a specific region.
• Higher reliability & performance over time
  Forge apps benefit from Atlassian’s scaling, monitoring, and ongoing platform improvements.
• Future-proof features
  Many new Atlassian capabilities and UI components arrive on Forge first. Moving now helps us ship improvements faster.

Good news: the migration is now in its final stages.
Our developers are exhausted, worn out, and have barely seen their families… but the sooner they finish everything, the sooner we’ll give them back their passports and let them celebrate Christmas. (Just kidding. Of course. But who knows? 🙂)

What we shipped in 2025 (the improvements you’ll actually use)

Even while Forge work was in progress, we released several meaningful updates to help teams analyze work faster and manage flow with less effort.

1) Enhanced Chart Options: clearer charts, better analysis, easier storytelling

To help you analyze data and make decisions faster, we expanded chart customization via the Chart Options button (top-right corner of the chart).

Show Percentages as Labels

What it does: converts chart labels into percentages, making it easier to compare proportions.
When enabled, tooltips also show percentage values.

Best for: quickly understanding distribution (“where time goes”) at a glance.

Trendline (for column charts)

What it does: adds a trendline showing linear progression on column charts.

• The trendline updates whenever chart data changes
• The formula appears directly on the chart:
  
  

y = Ax + B | R² = C

Where:

• y is the predicted Time in Status (or another metric you track)
• x is the time period (months, weeks, sprints, etc.)
• A is the slope (how much the metric changes per time unit)
• B is the starting value when x = 0
• R² shows how well the trendline fits your data (closer to 1 = stronger correlation)
  
  

Best for: answering “Are we improving?” without guessing.

Hide Labels

What it does: hides chart labels for a clean, uncluttered view—while tooltips still show values (or percentages) when you hover.

Best for: presentations and stakeholder-friendly charts.

2) FlagFocus by Time in Status: a Rovo agent that turns “Flagged” into a real signal

Blocked work is expensive—especially when you can’t clearly see where the waiting time accumulates.

That’s why we introduced FlagFocus by Time in Status, a Rovo agent that helps teams measure how long issues remain Flagged, and what statuses consume that flagged time (e.g., In Review, Waiting for Customer, In Progress, etc.).

What FlagFocus can do

Provide a JQL query and a time window. The agent scans issue history and turns flagged intervals into clear insights:

• Track total time issues are Flagged
• Break down flagged time by status
• See the percentage of flagged time spent in each status
  
  

Outputs

• Flagged Overview: Period • Filter • Total Flagged Time • Issue Count
• Flagged Time by Status: Period • Filter • Total Flagged Time + per-status breakdown

How it helps

• Triage faster: Escalate the statuses that accumulate the most flagged time (e.g., Waiting on Vendor)
• Fix root causes: Improve approvals, handoffs, or Definition of Ready where spikes happen
• Prioritize unblockers: Sort by longest-flagged issues and clear the path first

How to find it

Go to Chats → search “FlagFocus by Time in Status (Jira)” → open the agent.
Tip: Start with “Tell me about yourself.”

3) Smarter flow metrics on your board: group statuses into one metric in a custom field

This release is for teams who want KPIs visible directly on the board, without exporting data or manually stitching reports together.

Now you can group multiple statuses into one metric and show meaningful time-based KPIs on cards:

• Combine multiple statuses into a single time metric
• Track Lead Time, Cycle Time, Time to Resolution, etc. right on the board
• Stay schedule-aware: all metrics respect your working calendar (no nights or weekends)

Examples of grouping statuses into real metrics

• Lead time: group all statuses except the final one (everything except “Done”)
  → total time from creation until completion
• Active time: group only active/in-progress statuses (e.g., “In Progress,” “In Review,” “Testing”)
  → hands-on work time, excluding waiting
• Cycle time: group the delivery-phase statuses (e.g., “In Progress” → “Ready for Release”)
  → time spent moving through delivery
• Time to Resolution: group from first active status up to “Resolved/Done”
  → helpful for support-style workflows

End-of-year surprise: Sprint Report will support active sprints (coming soon)

Until now, Sprint Report has been available only for completed sprints.
In our next release, you’ll also be able to select an active sprint and see progress as it’s happening—without waiting for the sprint to close.

What will change for active sprints?

Because an active sprint is still evolving, the report will adapt accordingly:

• The report will show a Burndown chart (instead of Team Velocity)
• Metrics will update dynamically while the sprint is running
• Some values will be calculated from sprint start until “now”
• Carryover will be hidden for active sprints (it appears after completion)

If you’ve ever wanted to answer “How are we doing today?” without guesswork—this one is built exactly for that.

Beyond features: demos, events, and customer conversations that shaped the product

In addition to shipping releases, we presented Time in Status at events and webinars, spent many hours on demo calls, and held countless team brainstorms on how to make the app more helpful in the real world.

We kept listening. We kept adjusting. And we kept building with one goal: making Time in Status more useful—not just as a report, but as a decision-making tool.

Christmas greetings 🎄

And since we’re closing the year: thank you for being with us in 2025—for your feedback, your patience (especially during big behind-the-scenes work), and for telling us what actually matters in your Jira workflows.

Wishing you a Christmas with:

• fewer blockers than “Waiting for Customer,”
• fewer surprises than an unplanned scope change,
• and more joy than a perfectly flat burndown chart.
  
  

May your holidays be restful, your dashboards be calm, and your next sprint start with a clean board (we can dream, right?).

Merry Christmas and happy holidays — see you in 2026! 🎁✨