How long does Jira keep issue history?

“How long does Jira keep issue history?” has a reassuring answer and an uncomfortable one. The reassuring part — Jira keeps it for the whole life of the issue. The uncomfortable part — that life can end, and the history ends with it. Here is what is actually retained, and where the gaps are.

What Jira retains, and for how long

• Issue change history: the life of the issue. Every field change — status, assignee, priority, custom fields, old value to new value, author and timestamp — is kept on the issue’s History tab for as long as the issue exists. There is no time-based expiry while the issue is live.
• The admin audit log: per Atlassian’s policy. Jira’s site audit log records administrative and security-relevant events and is retained according to Atlassian’s platform policy. It is useful for “who changed this configuration,” but it is not a full per-issue field-change record, and it does not store an issue’s field content.

So for a living issue, history retention is effectively unlimited. The problem is not time — it is deletion.

The gap: deletion takes the history with it

Because the History tab is part of the issue, deleting the issue deletes its history. There is no separate copy left behind. The admin audit log will note that a deletion happened, but it cannot tell you what the issue contained or give the field history back — see how to recover a deleted issue in Jira for what your options actually are afterwards (they are thin).

This is the catch that surprises teams during an audit or an incident review: the history they assumed was permanent was only as permanent as the issue, and someone deleted the issue months ago.

How to keep history you control

The fix is an independent record, captured as changes happen and stored separately from the issue — not just a nicer view of the same native history. Trailkeeper’s free tier gives you a readable, searchable view of an issue’s native history; its paid tier adds a continuously-captured store with a retention policy you set (1 to 3650 days, default 90), so:

• History survives deletion. Because the paid tier captures to a separate store as changes happen, deleting the issue doesn’t erase what was already captured — though coverage only starts from when Trailkeeper was installed, not retroactively.
• You decide the window. Set retention to match your compliance needs rather than accepting whatever Jira’s defaults imply.
• It is exportable evidence. Export the captured history to CSV (uncapped on the paid tier) for an audit — see how to export Jira issue history to CSV.

The takeaway

Jira keeps issue history for the life of the issue — which sounds like “forever” until an issue is deleted and takes its history with it. If that history is evidence you might need later, do not rely on the issue surviving: capture it to an independent store with a retention policy you control, so “how long does Jira keep it?” becomes “as long as we decide to.”