Jira Cloud
Time in status for Jira —
every status change and worklog on a calendar and a roadmap
Jira knows when each issue changed status and when time was logged on it. Time in Status Calendar draws that history on a calendar and a Gantt-style roadmap, so you see where work waited, how long it stayed and who it was assigned to — and you can plan the next issues on the same calendar.
Free for up to 10 users on Jira Cloud · 30-day trial on every paid plan · no credit card · See pricing
The problem
Time in Status Calendar
Where the time actually went
None of this is missing from Jira. The change log records every status change and every worklog — it just does not show them to you in one place.
“How long was it stuck in review?” Someone opens the issue history and subtracts timestamps by hand, one issue at a time.
The timeline shows the plan. Start and due dates say what was supposed to happen, not when work really started, where it waited, or when it moved on.
Worklogs are there, scattered across issues. Nobody can see at a glance how much time went into which issue, on which day.
Some days one person has five things in progress, other days none. Nothing flags it until the sprint is already late.
The status report is rebuilt by hand. Someone exports issues every week to show the team’s progress, because the history in Jira cannot be read at a glance.
Plans and progress live in different places. Dates get set on one screen; what the issues did afterwards is buried in their history.
Why this app exists
Time in Status Calendar
Jira keeps the history. It does not draw it.
Jira’s issue history lists every change, one issue at a time. Jira’s timeline and calendar views show planned dates. Time in Status Calendar reads the same change log and worklogs and puts them on one timeline you can read across many issues at once.
| For the work you already track | Jira issue history | Jira timeline and calendar | Time in Status Calendar |
|---|---|---|---|
| What it shows | Every change, as a list | Planned start and due dates | Actual status changes and worklogs, on a timeline |
| How many issues at once | One issue | The issues in one project or board | Any projects you pick, narrowed by JQL |
| Time in each status | Timestamps you subtract yourself | — | A colored segment per status, on the days it happened |
| Worklogs | On the issue’s work log tab | — | A marker on the day, with comment and total, plus a daily summary |
| Dates you can plan by | — | Start date and due date | Any date or date-time field, including other apps’ fields |
| Work in progress per day | — | — | Min/max per day and swimlane, colored when exceeded |
What it does
Time in Status Calendar
Time in status, worklogs and plans on one timeline
Most time-in-status apps hand you a table of durations. This one draws the same history on a timeline, next to worklogs and WIP limits, so you see when the time went, not only how much.
Time in status on a roadmap
Every issue becomes a bar that starts when it enters a status you track and ends when it leaves. Each change between those statuses shows in its own color, so the bar’s length is how long the issue spent in them. Zoom from days to quarters.
You choose the statuses that count
Map the statuses you care about and give each a color. Out of the box, every status in the In Progress category is mapped and colored like its category — change the mapping to watch review, testing or any other stage. Work that has not ended yet fades out instead of stopping at a made-up date.
Worklog calendar
Time logged on an issue shows as a marker on the day it was logged, with a daily worklog summary. Hover for the time, the comment and the issue’s total, or log more time straight from the calendar or the roadmap.
Plan on a calendar
Put issues on monthly, weekly or daily views by any date or date-time field, including custom fields from other apps. Drag from start to end to schedule an existing issue or create a new one.
Swimlanes and daily WIP limits
Group the roadmap by project, assignee, priority, fix version or component. Set minimum and maximum work in progress per day for each swimlane; days outside the limits are colored, so queues and overload stand out.
Time in status gadget for Jira dashboards
Add the time in status roadmap or the calendar to any Jira dashboard as a gadget, with its own projects, JQL, status mapping, swimlanes, WIP limits and saved quick filters — so the weekly progress review opens on a dashboard instead of an export.
How it works
Time in Status Calendar
From your Jira projects to a roadmap of what really happened
Four steps, all inside Jira.
1
Pick the projects
Choose the projects to pull issues from — company-managed and team-managed both work — and narrow them with a JQL filter, or start with “Issues assigned to me”.
2
Choose the statuses that count
Map the statuses you want to see and give each a color. Turn worklogs on, and set daily WIP limits if you want overloaded days flagged.
3
Read the roadmap
Each issue’s bar shows when it entered, moved between and left those statuses, with worklog markers on the days time was logged. Group by assignee or fix version to see who is overloaded and where work queues up.
4
Put it on a dashboard
Add the roadmap or the calendar to a Jira dashboard as a gadget, and reuse the JQL quick filters you saved in the app.
Who it is for
Time in Status Calendar
Same history, four questions it answers
The same calendar and roadmap answer a different question for each role that runs delivery in Jira.
Scrum masters
Where did work wait this sprint?
Status colors show which issues sat in review or testing and for how many days — a concrete starting point for the retro.
Team leads
Who is carrying too much?
Swimlanes by assignee with daily WIP limits color the days someone had more in progress than agreed.
Project managers
What happened against the plan?
Plan issues on the calendar by their dates, then switch to the roadmap to see the status changes and logged time those issues really had.
Delivery leads
How are several teams moving?
One roadmap across projects, grouped by project or fix version, on the Jira dashboard you already share.
Trust & numbers
Time in Status Calendar
Built on Forge, with Atlassian’s own trust badges
From the team behind Release Management for Jira — an Atlassian Gold Partner, recognized five times in Atlassian’s partner awards. The numbers below come from this app’s Marketplace listing, October 2026.
Runs on Atlassian and Cloud Fortified on the Marketplace, part of Atlassian’s Marketplace Bug Bounty program, and covered by our SOC 2 Type II report.
Atlassian Gold Partner
SOC 2 Type II
120+
installs of Time in Status Calendar on Jira Cloud
3.5★
average rating across 5 Marketplace reviews of this app
2020
on the Atlassian Marketplace since, rebuilt on Forge in 2025
Setup & security
Time in Status Calendar
Installed from the Marketplace, drawn straight from your Jira change log
Nothing to provision and nothing to import. Your first calendar takes three choices: projects, an optional filter, and the date fields to plan by.
- A Jira admin installs it from the Atlassian Marketplace. There is no server to stand up and no separate account for your team to create.
- No data migration. It reads the status changes and worklogs already stored on your Jira issues, including everything from before you installed it.
- You choose who gets it. Access follows Jira’s global permissions: an admin decides which users and groups can open the app.
- It changes Jira only when you do. Scheduling an issue sets the date fields you picked, “New issue” opens Jira’s own create dialog, and time you log becomes a normal Jira worklog.
- Jira Cloud only. There is no Data Center version. It is built on Atlassian Forge, carries the Runs on Atlassian and Cloud Fortified badges, and is covered by our SOC 2 Type II report — the full posture is in our Trust Center.
- Support goes to our own service desk. Questions and bug reports reach the team that builds the app.
FAQ
Time in Status Calendar
Time in status for Jira — common questions
What is Time in Status Calendar?
Time in Status Calendar & Worklog Roadmap is a Jira Cloud app — a Jira plugin, in the older wording — that turns Jira’s change log into a calendar and a Gantt-style roadmap. You see when each issue entered, moved between and left the statuses you track, the worklogs on each day, and you can plan issues on the same calendar by any date field. It installs from the Atlassian Marketplace and is built on Atlassian Forge.
How does it show time in status?
You map the statuses you want to see and pick a color for each; by default, every status in the In Progress category is mapped. An issue appears on the roadmap when it moves into a mapped status, each change between mapped statuses shows in that status’s color, and the bar ends when the issue moves to a status you did not map. The length of each colored segment is the time the issue spent in that status. New to the metric? Start with how to measure time in status in Jira.
Does it give a time in status report with hours per status?
It draws time in status rather than tabulating it. Each status is a colored segment on the issue’s bar, so you see how long it lasted and when it happened, across many issues at once. If you need cycle time as a number, graded per issue and sprint, that is what issue and sprint health does. The metrics themselves are explained in flow metrics in Jira.
Can I see and log Jira worklogs on the calendar?
Yes. Turn worklogs on and every logged entry shows as a marker on its day; hover for the time, the comment and the issue’s total. Log more time straight from the calendar or the roadmap — it is saved as a normal Jira worklog. It is not a timesheet app: it shows time against issues on a timeline, not hours per person per week.
Can we plan work on the same calendar?
Yes. Pick any date or date-time field as the start and end — standard, custom, or a field from another Marketplace app — and the issues appear on monthly, weekly or daily views. Drag across the calendar to schedule an existing issue or create a new one; the app writes the dates back to those fields.
How is it different from Jira’s issue history and timeline?
Jira’s issue history lists the changes of one issue. Jira’s timeline and calendar show planned start and due dates. Time in Status Calendar reads the same history for many issues at once and draws what actually happened — status changes and worklogs — on a timeline, grouped by project, assignee, priority, fix version or component.
Is there a Data Center version?
No. Time in Status Calendar is a Jira Cloud app built on Atlassian Forge. Its Marketplace listing carries the Runs on Atlassian and Cloud Fortified badges, and security documentation is in our Trust Center.
What does it cost, and who installs it?
It is free for Jira Cloud sites with up to 10 users. Above that, it is licensed for the same user tier as your Jira site — that is how the Atlassian Marketplace licenses every app — and paid tiers start with a free 30-day trial, no credit card required. A Jira admin installs it, then chooses through Jira’s global permissions which users and groups can open it.
What happens if we stop using it?
Nothing in Jira changes. The app reads your issues, their history and worklogs where they already are. Dates it scheduled, issues it created and time logged through it are ordinary Jira data and stay on the issues.
Read before you install
Time in Status Calendar
See exactly how it works, in the product docs
Not ready for a trial yet? Each page below walks through one part of the app, with screenshots.
Docs
Getting started
Create your first calendar: projects, a JQL filter and the start and end date fields.
Docs
Status mapping and WIP limits
Which statuses draw a bar, how colors work, and how daily WIP limits are set.
Docs
The roadmap view
Zoom, swimlanes, quick filters and how each issue’s bar is drawn from its status changes.
Docs
Worklogs on the calendar
How logged time appears on the calendar and roadmap, and how to log time from there.
Docs
Planning on the calendar
Monthly, weekly and daily views, date and date-time fields, and scheduling by drag.
Docs
Dashboard gadgets
Gadget options, and a workaround for showing the gadget on a Confluence page.
Get started
See where your issues actually spent their time
Start a free 30-day trial from the Atlassian Marketplace, or book a walkthrough with our team.
Free for up to 10 users on Jira Cloud · 30-day trial on every paid plan · no credit card