Who Changed the Status? Identifying Issue Status Updates in Jira Data Center

[#1]

Teams can track issue status changes to increase the effectiveness of their projects and meet all the needed compliance standards. This function helps them monitor project development and maintain compliance standards. Understanding who modifies statuses and when it happens enables project managers, administrators, and team leads to maintain workflow efficiency and accountability.

Jira contains native features that help track status updates, yet users find it challenging to access these features for analysis. The History tab, JQL filters, and bulk change options help users gain insights. However, they must use them correctly to obtain meaningful results.

This article may be helpful for you if you are using Jira Data Center and need to identify who changed the issue status, filter relevant updates, or find out when the update happened.

Understanding status changes in Jira Data Center

Through workflows, Jira Data Center maintains a system to track issue status modifications, creating visibility and providing accountability. When an issue changes its status (e.g., To Do → In Progress → Done), Jira automatically records the event as well as who made the change and when it occurred, along with any comments added.

The History tab under the issue view shows all changes with status updates and other modifications. The Activity Logs show complete issue modification records spanning across all projects.

Tracking status changes in Jira Data Center is essential for reporting and workflow management. Why? That’s because it allows teams to analyze processes more efficiently and identify bottlenecks quickly.

How to view single issue status changes in Jira Data Center via the History tab

Within the Jira Data Center, the History tab shows a complete record of all modifications that occur to an issue, including changes to its status. You can view status changes by following these steps:

1. Open the needed issue. Navigate to the issue you want to review.
2. Access the History tab. In the Activity section below the main issue details, you will see options such as All, Comments, Work Log, and History. Click on the History tab.
3. Review the change of status. The chronological display in the History tab shows complete records of issue modifications, including information about the user who changed the status and when it occurred.

This method enables monitoring of how issues move between different statuses, which shows both their historical development and the work performed by team members.

Using Jira Data Center filters to view multiple issue status changes

Jira's native capabilities to filter and display status transition histories and users responsible for that are pretty limited, but you can leverage Jira Query Language (JQL) to gain more insights. Just follow these steps:

1. Go to Issues and then select Search for Issues.
2. Switch to Advanced Search (JQL mode).
3. Use a JQL query to find the issues in a specific project, view information on their status changes, and identify the user responsible for it. For example:

project = MAR AND status changed FROM "In Progress" TO "Done" and status CHANGED BY currentUser()

Note: Historical status change details (date, previous status, and what user changed it) are not available natively in JQL. For extended functionality, you must check the History tab inside an issue or use a Jira add-on like Issue History for Jira.

Using Issue History for Jira add-on for identifying multiple issue status updates in Jira Data Center

With the Issue History for Jira add-on, you get a central view of all issue changes, which helps you track status updates and the users responsible for all the issue changes.

Follow these steps to use it:

1. Go to Atlassian Marketplace, search for Issue History for Jira, and click "Try it free”. Choose your Jira Data Center deployment and follow the installation steps.
2. After installation, go to Apps > Issue History for Jira.
3. You can filter results by Project, Issue Key, User, Date Range, and Status Change.
4. Identify Responsible Users: The table displays who changed the status, when, and the old → new value.

Reasons to try to use Issue History for Jira add-on:

• It keeps track of changes on multiple issues in one shot (Jira's built-in History tab only tracks changes on a single issue at a time).
• You can use filters to find status transitions quickly.
• It shows all the data relevant to one table, including who changes the status and when.
• It supports export for audit and reporting.

Summing Up

The ability to identify issue status updates in Jira Data Center is crucial for workflow transparency, accountability, and efficient project management. Jira’s built-in History tab, Audit Log, and JQL filters can help track changes, but they don’t work well when looking at many changes at once. With the Issue History for Jira add-on, you get a simpler, more efficient view of who changed the status, when it was changed, and what the previous and new statuses were, all in one place. Using these tools allows teams to track progress, prevent bottlenecks, and maintain a smooth workflow.