Issue History Reporter for Jira – New Ways to Feed Data and Issue Snapshot Report Type

[#1]

Over the past months, Issue History Reporter for Jira has evolved based on feedback and requests from the Atlassian Community. The focus has been on giving users more control over how work items are selected and more precision in historical analysis.

This article highlights the most important additions.

---

🔍 More flexible ways to feed work items into reports

Originally, Issue History Reporter for Jira allowed feeding data primarily by Project.

Users asked for more flexibility, especially in large Jira instances or cross-project scenarios. As a result, the app now supports feeding work items using multiple criteria, allowing much more targeted and efficient reporting.

You can now feed work items by:

• Assignee

• Filter

• Issue

• Issue Type

• Label

• Project

• Summary

• Creation Date

• Priority

• Reporter

• Status

• Sprint

• Version

This makes it easier to:

• focus on exactly the issues you care about

• work across multiple projects without noise

• reuse existing Jira filters

• limit data volume while increasing relevance

---

🔎 Two-stage precision: feed first, then filter

In addition to the expanded Get work items by options, the initially loaded data can be further filtered using the same set of fields.

This creates a powerful two-stage workflow:

1. Feed issues broadly using one or more criteria

2. Refine the result set using the same fields as filters

For example:

• feed issues by Project and Issue Type, then filter by Assignee and Status

• feed by Filter, then narrow results by Sprint or Priority

• feed a wide historical set, then iteratively refine it without reloading data

This approach gives users:

• much finer control over the final dataset

• faster iteration without repeating expensive data loads

• the ability to explore and refine results interactively

For many users, this combination of flexible data feeding + consistent filtering becomes a key productivity feature.

---

🕒 New report type: Issue Snapshot

Another frequently requested capability from the community was the ability to see how issues looked at a specific point in time, not just how they changed over time.

To address this, a new report type has been introduced:

Issue Snapshot

With Issue Snapshot, you can:

• select a specific date

• view the state of each issue as it was at that moment

• see field values exactly as they existed then

This is useful for:

• audits and compliance checks

• post-mortems and retrospectives

• historical reporting

• answering “what did this issue look like on that date?”

Issue Snapshot complements Issue History:

• Issue History explains how issues changed

• Issue Snapshot shows what the issue looked like at a given moment

📌 Why these changes matter

These enhancements move the app beyond a project-centric view and toward precision reporting:

• flexible, multi-criteria issue selection

• consistent filtering on already-loaded data

• better alignment with how teams actually work in Jira

• clearer historical understanding of work items

The goal remains the same: provide accurate, exportable issue data that users can analyze in their own tools (Excel, Power BI, AI tools, etc.).

---

🔁 Final note

The expanded data-feeding options, consistent filtering model, and the new Issue Snapshot report were all introduced in response to requests from the Atlassian Community. Feedback continues to shape the direction of the app, and further improvements are planned along the same principles.

If you have use cases or ideas you’d like to see supported, feel free to share them.