Jira Audit Log: A Step-by-Step Guide to Reviewing Changes
Need to trace who changed Jira settings and when? This step-by-step Jira audit log guide helps you find the right records. Read now.
A Jira audit log records administrative and configuration changes, helping you investigate who changed settings and when. When permissions shift or an integration stops working, unclear change history can slow down your response.
The challenge is that the audit log does not show every change to every issue. If you rely on it alone, you may miss important activity recorded in an issue’s own history or in a separate organization-level log.
But here's the truth: reviewing changes is straightforward when you know which log to check, how to narrow the results, and what evidence to preserve. This guide walks you through those steps and explains how to handle common gaps.
How to Review the Jira Audit Log Step by Step
Start with the Jira audit log for administrative events, then check issue history or organization-level records when your investigation requires a wider view. The exact menus and available filters can vary by Jira version and permissions.
- Confirm your access. Sign in with an account that has the relevant Jira administration permissions. If you cannot see the audit log, ask a Jira administrator to check your access.
- Open the right audit log. In Jira, look under the administration settings for
System and then Audit log. For organization-wide activity in Atlassian Cloud, an organization admin may need to review the security audit log in Atlassian Administration.
- Set a focused time range. Choose the period around the event you are investigating. For example, if a permission changed Tuesday morning, begin with the hours before and after that change.
- Filter the results. Use available categories, users, or other filters to reduce unrelated entries. Try a broader search if you do not know who made the change.
- Inspect the relevant entry. Check the actor, time, event type, and details shown. Compare the entry with what you expected to happen, such as a group membership update or configuration change.
- Check related histories. If the event involved an issue, review that issue’s activity or history. For organization, access, or security events, check the relevant organization-level records too.
- Preserve and communicate findings. Use an available export or approved capture method if you need to share the results. Record the time range and log area you checked, then follow your organization’s security process.
Here's why this sequence works: you establish the log’s scope before drawing conclusions. A missing entry may mean you checked the wrong history, time range, or administrative level.

What the Jira Audit Log Records
The Jira audit log is an administrative history that helps you review events affecting Jira configuration and management. Depending on the product version and setup, entries may cover changes to settings, users, groups, permissions, or integrations.
Each entry can include details such as the person or account that performed an action, the event time, the event category, and a description of the change. The detail available varies, so inspect the specific entry rather than assuming every record contains the same fields.
For example, if a team member loses access to a project, an administrative event may help show whether a group or permission setting changed. To see edits to a particular issue, you may need to inspect that issue’s history instead.
The best part? Treating these histories as complementary makes investigations more complete. The Jira audit log covers administration; issue history and organization-level logs cover other parts of the activity picture.
Choose the Right Log for the Change
Jira activity can appear in different places, depending on what changed. Before searching, identify whether you are investigating an administrative setting, an issue update, or an organization-level event.
- Jira audit log: Useful for administration and configuration activity within Jira. Start here for questions about settings, permissions, and management changes.
- Issue history or activity: Useful for changes to an individual issue, such as status, assignee, or edited fields. Open the issue and review its available history.
- Organization-level audit log: Useful for events managed at the Atlassian organization level, such as certain security or access activities. An organization admin may need to review it.
Consider a case where a project’s workflow changed and a particular issue also moved unexpectedly. The Jira audit log may help explain the workflow configuration change, while the issue history can show the individual issue’s transition.
Let me explain: the event you need may not appear in the first place you look. Match the log to the object or setting involved before deciding that no record exists.
How to Read an Audit Entry Carefully
Read each entry as evidence of a recorded event, not as a complete explanation of everything that happened. The log can identify an action while leaving the business reason or surrounding discussion elsewhere.
Check the actor and timestamp first. Confirm the time zone used in the interface, especially when comparing activity across teams in different regions. Then inspect the event details and identify the exact setting or object involved.
For example, an entry may show that a group’s permissions changed at 10:15. That does not, by itself, explain why the change was approved or whether the group membership also changed. You may need to check a related access history or ask the relevant administrator.
When you share findings, separate what the entry confirms from what you infer. That distinction helps avoid treating a timestamp or account name as proof of intent.
Retention, Access, and Investigation Limits
Audit-log access and retention can vary by Jira product, plan, configuration, and organization policy. Check your environment’s current settings and product guidance before relying on a particular time span or export option.
Some records may be visible only to administrators. If you do not have the required permission, request a review from the appropriate Jira or organization admin rather than trying to work around access controls.
You might be wondering: what if the event is older than the available history? Ask your administrator whether another approved monitoring or retention process applies. For future investigations, agree on who reviews logs and how important findings are preserved.
For a practical example, a support team could agree that project administrators review permission changes weekly, while security staff handle organization-level access concerns. Clear ownership makes it easier to respond when an alert arrives.
Jira Audit Log Workflows: ONES.com as a Project Management Option
ONES.com is a unified project management and knowledge management platform powered by ONES Assistant. ONES Project provides project management and is positioned as a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

ONES Project can help teams organize workflows, fields, sprints, automation, and reporting in one project environment. These capabilities support process visibility, but they are not a claim that ONES Project provides the same audit-log functions as Jira. Confirm the required audit and compliance controls for your own environment before making a platform decision.
Value Proposition
If your team is reviewing its project-management setup, ONES Project offers Jira-compatible workflows, built-in reporting, and deployment choices that include cloud and self-hosted environments. You can evaluate its workflow governance alongside your specific audit, access, and retention requirements.
Core Capabilities
- Scattered project updates: ONES Project brings project work into a project-management environment, helping teams keep task progress easier to follow.
- Workflow changes that are hard to coordinate: Custom workflows let teams shape project stages around their process, giving participants a consistent path for work.
- Fields that do not fit the team’s process: Custom fields capture relevant project details, which can make work items more informative for the people managing them.
- Sprint planning overhead: Sprint management supports planning and tracking work in iterative teams, helping people review what is in progress.
- Repeated manual actions: Automation can handle selected routine workflow actions, reducing the need for team members to repeat the same steps.
- Limited visibility into project status: Built-in reporting helps teams review project progress and identify areas that may need attention.
- Migration concerns for Jira teams: Jira-compatible workflows can make it easier to assess how existing processes may translate. Validate the details of your workflows during evaluation.
- Deployment constraints: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. The company states that its cloud and self-hosted versions have full feature parity.
Application Scenarios
A software team considering a Jira alternative could test its sprint process, custom fields, and reporting in ONES Project. During evaluation, the team should separately verify that its required administrative audit controls meet internal policy.
An organization with restricted-network requirements could assess the Air-gapped or other self-hosted deployment options. Its administrators can compare operational needs, access controls, and audit expectations before selecting a deployment.
ONES.com offers a free tier for up to 30 seats. Teams can use that allowance to evaluate project workflows, then assess deployment and governance requirements before wider adoption.
Common Challenges When Reviewing Changes
- The expected event does not appear. You may be checking an administrative log for an issue-level edit. Review the issue’s history and confirm that you selected the correct time range.
- The log shows an event without enough context. An entry may record what changed without explaining why. Compare related histories and consult the administrator or team responsible for the change.
- You cannot access the relevant log. Audit records may require administrator permissions. Request a review from a Jira or organization admin and explain the event, time range, and reason for the check.
- The event is outside the available history. Retention differs across environments. Check the applicable policy and ask whether an approved monitoring process retains older records.
FAQs
Where do I find the Jira audit log?
In Jira, look in the administration settings under System and then Audit log. The exact route can vary by Jira version and permissions. For organization-level activity in Atlassian Cloud, an organization admin may need to open the audit log in Atlassian Administration. If you cannot see the relevant area, ask an administrator to confirm your access and check the right log.
Does the Jira audit log show every issue change?
No. The Jira audit log focuses on administrative and configuration activity. Changes to a specific issue, such as its status, assignee, or field values, are generally reviewed through that issue’s history or activity view. If you are investigating a wider access or security event, an organization-level log may also be relevant. Check each history that matches the change you are trying to understand.
Can I see who changed a Jira permission?
The Jira audit log may show permission-related administrative events, including the actor and event details available in your environment. The information shown can vary by version and configuration. If the event is missing or incomplete, confirm the time range and check whether the change happened at the project, Jira, or organization level. An administrator may have access to records that are hidden from other accounts.
How long does Jira keep audit-log entries?
There is no single retention period that applies to every Jira environment. Retention can depend on the product, plan, and configuration, while organization policies may define additional requirements. Check the current settings and guidance for your environment before relying on older entries. If your team needs longer retention, ask an administrator or security team which approved monitoring and record-keeping practices apply.
Conclusion
A Jira audit log is a useful starting point for reviewing administrative and configuration changes. Find the right log, narrow the time range, inspect the entry, and check issue or organization histories when the event requires more context.
When a record is missing, access is limited, or the available history is too short, involve the right administrator and follow your organization’s review process. If you are evaluating project-management workflows, ONES Project is a Jira alternative to assess separately from your audit and compliance requirements.