A common challenge when analyzing work in Jira is answering a simple but often unsupported question:
“What did this issue look like at a specific point in time?”
Jira provides detailed change history, but it does not offer a native way to view the complete state of an issue — across all fields — as it existed on a chosen date.
To address this gap, Issue History Reporter for Jira, released by our team, now includes a new report: Issue Snapshot.
The Issue Snapshot report reconstructs and displays the full state of issues at a selected date and time.
For each issue, the report shows the field values exactly as they were at that moment, including:
Status and status category
Assignee, reporter, priority
Versions, resolution, due date
Description, comments, attachments
Custom fields and system fields
The report answers the question:
“If I had opened this issue on that date, what would I have seen?”
Many reporting and audit scenarios require understanding state, not just events. Examples include:
Compliance and audit reviews
Incident post-mortems
Contractual or regulatory evidence
Historical analysis beyond workflow transitions
While issue history explains how things changed, the Issue Snapshot report shows what the issue looked like at a specific point in time.
Users select their usual filters (project, issue type, users, fields, etc.) and provide a required Issue Snapshot Date.
The report reconstructs the issue data as of that timestamp and displays the results in a tabular format.
As with other reports in Issue History Reporter, the data can be exported to CSV for further analysis or archival purposes.
The Issue Snapshot report complements existing history-based reporting rather than replacing it:
History reports explain when and how changes occurred
Snapshot reports show the full issue state at a chosen moment
Together, they provide a more complete understanding of how work evolved over time in Jira.
Petru Simion _Simitech Ltd__
President
Simitech Ltd.
Calgary, CA
10 accepted answers
0 comments