When you look at your projects and issues, what is the first info you check? Were there any status updates, new comments, or due dates added? Tracking changes in Jira isn’t just about curiosity, it’s about control. Managers, team leads, and developers all need to know what changed, when it changed, and who made the update.
Everyone wants to stay informed, track updates, and avoid any risk regarding customers' dissatisfaction with delivering a product/project/feature not on time. So, here we will look at the options you have with Jira natively and Jira add-on to get a history of changes for any field for the list of issues in your projects or other filters.
Jira Query Language allows history searches with WAS or CHANGED operators. It also has limitations on fields. You can only view changes for six fields: Assignee, Fix Version, Priority, Reporter, Resolution, and Status. Let’s look at some examples.
Example 1. Find issues that had their fix version changed during the week:
fixVersion CHANGED AFTER -1w
Example 2. Find issues that had their priority changed within a specific time frame:
priority CHANGED DURING ("2023/01/01", "2023/12/31")
Example 3. Find tickets that changed status to CLOSED in the last 24 hours.
Status = “Closed” and status CHANGED DURING (-1d, now())
In fact, JQL doesn’t show the changes themselves, only issues where these fields were updated. So, it’s not like the History like the one you can see under the Activity section of each issue.
The new option of Issue History for Jira allows you to filter by specific field and see its history. It is called Activity view and captures changes for any standard or custom field and presents them in clear view with colors and highlighting.
What you will get:
🌟 And the main option is the field selection, where you can choose one, two, or multiple fields where you want to see changes.
Choose a project you need or another filter (updater, time) to narrow the selection.
Select the status field in the field selector.
Choose a project you need or another filter (updater, time) to narrow the selection.
Select the due date field in the field selector.
Choose a project you need or another filter (updater, time) to narrow the selection.
Select the assignee field in the field selector.
Choose a project you need or another filter (updater, time) to narrow the selection.
Select the comments field in the field selector.
*Note: History records only when someone add delete comment, not content changes like replacing word. It’s limitation of Jira applicable only to this field.
Choose a project you need or another filter (updater, time) to narrow the selection.
Select the description field in the field selector.
So, you can get history of all fields for issues in your projects, or select the specific field to review its changes.
How to find this option:
If you want to get custom field changes, read more in How to see custom field history in Jira
Jira provides some built-in ways to search for changes, but they’re limited. If you only rely on JQL, you’ll quickly discover it covers just a handful of fields. For everything else — comments, descriptions, custom fields — you’ll need another solution.
The Issue History for Jira app offers a way to see those changes in one place, with filters for projects, people, and time frames. You can review field updates across many issues at once and focus on the details that matter to your team.
→ Explore the reports in the Issue History for Jira app and select the most convenient view.
Yuliia_Borivets__SaaSJet_
0 comments