How to Get Details on User Activity in Jira Data Center

[#1]

For team leads and managers, it is important to understand what is happening in Jira Data Center – who made changes, when they did it, what was changed. Tracking user activity enables them to stay up-to-date with their team’s work, find out whether tasks progress or not, and ensure that everyone adheres to the process.

It also allows for detecting problems early, such as delays or missed updates, and can make it easier to answer questions from other teams or stakeholders. In other words, tracking user activity helps to control the team and prevent the projects from going off the rails.

Native Jira Data Center Features for Tracking User Activity

History Tab

Each issue in Jira Data Center has its own History tab that provides a comprehensive log of all the changes that were made to that issue over time. This includes the updates to such fields as:

• Status (For example, To Do → In Progress)
• Assignee (the one responsible for the task)
• Priority, labels, and other custom fields

It is a suitable method for monitoring user activity on one issue – who changed what and when – but there are some limitations to it.

⚠️ Limitations:

• It is only possible to see the history of one issue at a time.
• It is not convenient for audits, reporting, or a complete history of a project.
• History search or export is not available natively.

Using JQL

Jira Query Language (JQL) is a convenient way to search for issues using certain criteria, such as the actions taken by users. Though it won’t provide you with a complete activity history, JQL may assist you in finding the issues where a user was recently active, with some limitations.

🔍 Useful JQL Examples:

• To search for issues in the exact project that were changed by the specific user during the last 7 days, you can use the following JQL query:

project = MARKETING AND issuekey in updatedBy("John Smith", "-7d")

 

• To find the issues with comments by a user after a specific date, you can use such a JQL query:

issueFunction in commented("by admin after '2025-05-10'")

• To get issues that reached the "Done" status by a specific user during the current week in Jira Data Center, you can try the following JQL query:

status = Done AND status CHANGED BY "admin" AFTER startOfWeek()

⚠️ Limitations of JQL for tracking user activity:

• JQL does not allow filtering by the particular change of the field (e.g., “who changed the due date”).
• It cannot demonstrate a timeline of actions taken by a user on several issues.
• There is no native support to track or export user activity over time.

Usage of Issue History for Jira App for Tracking User Activity

For teams who need to track user activity across multiple issues, the Issue History for Jira app offers extra tracking options that are not present in Jira Data Center's native functions. It enables users to see all the changes made to issues — who made them and when — across all projects and time periods. This can be particularly useful for auditing, reviewing team contributions, or getting the complete history of changes in specific periods.

Issue History Tab – Detailed Activity Per Issue

The Issue History tab, which is added to each issue’s view, helps to monitor all changes that were made to this particular issue in a clean timeline. You’ll find:

• Who made the change, and when
• What field was modified (for example, status, description, comment, assignee, priority)
• Use the filter on the fields (for example, you can choose to see the changes only made to issue descriptions)
• The previous and new values

This makes it easy to quickly and easily see how the issue progressed.

Table View – Cross-Issue User Activity Tracking

For wider monitoring, the Table view of the Issue History app allows you to view a complete history of multiple issues, filtered by user, project, date, or specific fields. This centralized history view includes:

• Changes made by a specific user
• Filter options for dates, fields, etc.
• Export to CSV or Excel for reporting/auditing

It is perfect for managers who need to monitor user activity, detect inconsistencies, or check whether there is activity in a team during a sprint or project period, without the need to open issues one by one.

Let’s explore the example of using a Table view to monitor user activity. Suppose you are a project manager and have to track the activity of a particular team member during a sprint. Using the Table View, you can monitor all user activities on several issues.

You can also export a table to a CSV or Excel file so you can share it with your colleagues or use it to report on and have a complete record of what the user did during the required period.

This makes it easy to monitor progress, track performance, and keep everyone on task in the sprint.

📊🚀Track user activity with ease. Try the Issue History for Jira app on Data Center today! 

☁️🔍 Monitor user activity seamlessly. Try the Issue History for Jira app on Cloud now! 

Summing Up

User activity monitoring in Jira Data Center enables teams to remain transparent, accountable, and in control of project development. It enables the manager to know who made certain changes and when they occurred.

Jira’s built-in functionality provides basic visibility through per-issue history and simple JQL queries. However, they fail to present a full picture of the user activity. Apps such as Issue History for Jira allow tracking who changed what, as well as when and on which issues. This makes it easier, for example, to audit actions, monitor teamwork, and generate accurate activity reports.