Jira issue history tab is not showing change for some fields
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When viewing Jira issue history tab, it seems to be omitting the history of certain fields.
For example:
- You can see that the Sprint field for an issue has been defined as "Sprint 1"
- When checking the issue history tab, there is no indication of when this value had been set to "Sprint 1"
Environment
Jira Server/Data Center on any version from 7.0.0.
Cause
Root Cause 1
The issue history entries had been removed from the database
Root Cause 2
A third-party add-on is blocking the issue history from being displayed, for example: Field Security Plugin for Jira
Note that another side effect of using the add-on Field Security Plugin for Jira is the fact that automation rules using the Field Value Changed trigger might not be triggered as expected, as explained in the KB article Automation For Jira - Some automation rules using the "Field value changed" trigger are not triggered.
Resolution
Resolution for Root Cause 1
If the history has been removed from the database:
- The only method to recover this history would be from a backup before the change was made.
- Restoring this backup would also mean losing data between the time of backup until current day
Resolution for Root Cause 2
If the history is being blocked by a third-party add-on:
- Determine why the add-on is blocking your fields and configure it properly
- Or, disable/remove the add-on.
- In the case of the add-on Field Security Plugin for Jira, disabling this plugin will require a restart of Jira to observe the changes.