Where does the history come from?

From Jira's own changelog, read through the Jira REST API as the signed-in user. The app fetches the complete history of each issue, not only the most recent changes.

Can users see history for issues they can't access?

No. Every request runs with the viewing user's permissions, so people only ever see history for issues they can already browse in Jira.

Is my Jira data stored or sent anywhere?

No. The app runs on Atlassian Forge and declares no egress, so issue data is never sent to external servers. The only things it stores are each user's saved searches and settings, in Atlassian's Forge storage.

How is time in status calculated?

From the moment an issue enters a status until it leaves it, starting from the issue's creation date. You can measure calendar time or business hours, and repeat visits to the same status are added up.

Does it understand custom workflows?

Yes. It uses each status's Jira category (To Do, In Progress, Done), so custom statuses such as Shipped or Won't Fix count correctly for cycle time and completion.

Yes, for status, assignee, priority and summary. Restore uses Jira's normal edit and transition permissions, so it only works where the user could make that change in Jira anyway.

Does it work with Company-managed and Team-managed projects?

Yes. It reads the standard Jira changelog, which both project types record.

for JiraRuns on Atlassian

Issue History+ for Jira

Every change to every issue, time in status and insights, in one place

Search the complete change history of your Jira issues, see how long work spends in each status, and spot stuck work, rework and SLA breaches. It runs entirely on Atlassian Forge, so your issue data never leaves Atlassian.

Get it on the Marketplace Read the docs

Issue History+ for Jira running inside Jira

What Issue History+ for Jira does

Complete change history
Every field change for the issues you choose, by project, sprint, assignee, label, JQL or a list of issue keys
Time in status
Median and 85th-percentile time per status, per-issue breakdowns, business hours and SLA thresholds
Status timeline
Each issue's journey through your workflow on one timeline, coloured by status category
Insights
Cycle time, weekly throughput, inactive work, reopened issues, rework and SLA breaches
Issue Insights in every issue
A tab in each issue's Activity section with time in status, the status timeline and every change
PDF, Excel and CSV exports
Branded PDF reports with your logo, plus Excel and CSV for further analysis
Word-level diffs and Restore
See exactly what changed in summaries and descriptions, and put status, assignee, priority or summary back
Saved and recent searches
Private bookmarks and your last searches, one click away

What changes for your team

Answer "who changed this, and when?" for any set of issues in one search instead of opening each issue's History tab
See how long work really sits in each status, with medians and the time 85% of visits finish within, not averages skewed by one stuck issue
Find stuck work before stand-up: issues that are not done and have had no status change for 7, 14 or 30 days
Measure rework and reopened issues from the history Jira already records, with no extra fields or workflow changes
Flag SLA breaches per status, in calendar time or business hours
Share a branded PDF, Excel or CSV report with stakeholders who don't use Jira