Skip to main content

How to Export Jira Audit Logs for Compliance and Security Reviews

· 6 min read
NGPilot
Quick Answer

Jira audit logs track who changed what, when, and where. Export logs to CSV or via REST API for compliance audits, security investigations, and change management documentation.

What you'll learn
  1. How to access and navigate the Jira audit log
  2. How to filter audit entries by user, date, and action type
  3. How to export audit data to CSV or via REST API
  4. How to set up automated logging and retention policies
  5. How to analyze audit data for compliance and security

Audit logs are the paper trail of your Jira instance. They record who did what, when, and where — essential information for compliance audits, security investigations, and change management.

Without proper audit logging, you cannot prove who deleted that issue, when permissions changed, or whether someone accessed restricted data. This guide covers how to access, export, and analyze Jira audit logs.

Why Audit Logs Matter​

Audit logs serve multiple purposes:

Compliance. Many regulations (SOC 2, ISO 27001, GDPR) require documented change trails. Jira audit logs provide this evidence.

Security investigations. When something goes wrong — unauthorized access, data deletion, permission changes — the audit log tells you what happened and who was involved.

Change management. Track configuration changes, workflow modifications, and permission updates to understand how your Jira instance evolved.

Dispute resolution. When there is a disagreement about who changed what, the audit log is the source of truth.

How to Access the Jira Audit Log​

Jira Cloud​

  1. Go to Jira Settings > System > Audit Log
  2. Use the date range picker to select a time period
  3. Filter by:
    • Category — Issues, Projects, Permissions, etc.
    • Action — Created, Updated, Deleted, etc.
    • User — specific user who performed the action
  4. Click Export to download a CSV

Jira Server/Data Center​

  1. Go to Jira Settings > System > Audit Log
  2. Click Advanced Audit Log for detailed entries
  3. Use the search bar to filter by keywords
  4. Click Export to download

What the audit log tracks:

CategoryWhat It Records
IssuesCreation, updates, deletion, transitions, comments
ProjectsCreation, configuration changes, deletion
PermissionsScheme changes, role assignments, group modifications
WorkflowsSchema changes, transition additions
UsersAccount creation, deactivation, group membership
SystemConfiguration changes, plugin installations

How to Export Jira Audit Logs: Step-by-Step​

1. Access the Audit Log​

Navigate to the audit log in your Jira version:

Jira Cloud:

Jira Settings (gear icon) > System > Audit Log

Jira Server:

Jira Administration > System > Advanced Audit Log

2. Filter Audit Log Entries​

Use the built-in filters to narrow results:

Filter by date:

  • Select a start and end date
  • Use presets: Last 24 hours, Last 7 days, Last 30 days

Filter by category:

  • Issues — all issue-related changes
  • Projects — project creation and modification
  • Permissions — access and role changes
  • Users — account changes

Filter by action:

  • Created — new items
  • Updated — modifications
  • Deleted — removals
  • Transitioned — workflow changes

Filter by user:

  • Enter a username to see all actions by that person
  • Useful for insider threat investigations

3. Export Audit Log Data​

CSV export (simple):

  1. Apply your filters
  2. Click Export (top right)
  3. Choose CSV format
  4. Download and open in Excel or Google Sheets

REST API export (programmatic):

# Get audit records from the last 30 days
curl -u admin:password \
  "https://your-domain.atlassian.net/rest/api/2/auditing/record" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "2026-06-29T00:00:00.000Z",
    "to": "2026-07-29T23:59:59.999Z",
    "filters": ["category:issues"]
  }'

For large exports:

  • Use the API with pagination
  • Export in batches (e.g., 7-day chunks)
  • Store in a database or SIEM tool

4. Set Up Automated Audit Logging​

Retention policy:

  • Jira Cloud: 60 days default (upgrade for longer retention)
  • Jira Server: Configurable (default 90 days)
  • Best practice: Export weekly and archive for 1 year+

Automated exports:

  1. Create a script that calls the audit log API
  2. Schedule it with cron (Linux) or Task Scheduler (Windows)
  3. Store exports in a secure, immutable location
  4. Set up alerts for sensitive operations (permission changes, deletions)

Sensitive operations to monitor:

  • Permission scheme changes
  • User role assignments
  • Issue deletions
  • Workflow modifications
  • System configuration changes

5. Analyze Audit Log Data​

In Excel/Google Sheets:

  1. Import the CSV
  2. Sort by date to see chronological changes
  3. Filter by user to see individual activity
  4. Filter by category to focus on specific changes
  5. Create pivot tables for summary views

In a SIEM tool (Splunk, ELK, etc.):

  1. Ingest audit log CSV or API data
  2. Create dashboards for:
    • Daily change volume
    • Top users by activity
    • Permission changes over time
    • Anomaly detection (unusual access patterns)
  3. Set up alerts for suspicious activity

Key metrics to track:

  • Total changes per day/week/month
  • Changes by user (identify outliers)
  • Permission changes (security-sensitive)
  • Issue deletions (data integrity)
  • Failed login attempts (security)

FAQ​

What does the Jira audit log track?​

The audit log tracks user logins, issue changes (creation, updates, deletions), project changes (creation, configuration, deletion), permission changes, workflow transitions, and administrative actions. The level of detail depends on your Jira version and licensing.

How long does Jira keep audit log data?​

Jira Cloud keeps audit logs for 60 days by default. Jira Server/Data Center retains logs based on your configuration (default 90 days). For longer retention, export logs regularly and store them in an external system.

Can I export Jira audit logs via API?​

Yes. Jira provides REST API endpoints for audit log data. Use the /rest/api/2/auditing/record endpoint to query audit records programmatically. This is useful for large exports or integration with SIEM tools.

How do I track who changed a specific Jira issue?​

Go to the issue > Click History tab to see all changes. For bulk tracking, use the audit log with filter category 'Issues' and the issue key as the search term. The audit log shows who changed what and when.

Is the Jira audit log sufficient for SOC 2 compliance?​

The audit log provides a baseline, but SOC 2 requires more: access reviews, change management documentation, and incident response procedures. Use the audit log as one input into your compliance program, not the entire solution.

Try Simple Bulk Issues Excel CSV Export for Jira

Export filtered Jira issues to Excel (XLS/XLSX) or CSV with custom fields and JQL — free for up to 10 users.

Get it on the Atlassian Marketplace →

Related guides