Jira · Compliance Log Vault

Keep Jira audit logs longer than 180 days

Retain Jira audit records long-term and export SOC 2 and ISO evidence. Runs entirely on Atlassian.

Try it free on the Atlassian Marketplace Documentation

Runs entirely on Atlassian Forge inside your own tenant. No external servers, no data egress.

Why it exists

This app answers a request that has been open on Atlassian's public tracker for years: JRACLOUD-68267, "Jira audit log retention period needs to be increased", with 224 votes.

The gap

Jira's native audit log is capped: records older than roughly 180 days age out and are gone. When a SOC 2 or ISO auditor asks for last year's evidence, there is nothing to show. Raising the cap is one of the longest-standing open requests on the public tracker.

What it does

Daily incremental sync of new Jira audit records into an in-tenant vault.
Dedup by record id: a record is never stored twice, even across overlapping syncs.
Long-term retention past Jira's cap; the vault only grows.
Browse retained records newest-first from an admin page.
Retention stats: counts by day and category, and the full retained span.
One-click, audit-ready CSV export of the whole vault.

The vault: every retained audit record, browsable newest-first.

Retention at a glance: coverage by day and category, and the full span you can prove.

The daily sync pulls new records, dedups by id, and appends to the vault.

60-second walkthrough

Honest about its limits

Capture starts at install. Records that had already aged out of Jira's window before install cannot be recovered.
The vault stores Jira audit records; it does not capture org-level (admin.atlassian.com) audit events, which live behind a different API surface.
Read-only. This app reports and exports; it changes nothing in your instance.

Security & permissions

Built on Atlassian Forge: the app runs on Atlassian's own serverless platform inside your tenant, stores its data in Forge storage, and makes no external network calls. Every scope it requests, and why:

read:audit-log:jira	reading the audit records
read:user:jira	required pair for the auditing endpoint
storage:app	the vault itself, in your tenant

The native feature it builds on

Atlassian's own documentation for what Jira does out of the box, so you can see exactly where the gap is:

Audit activities in Jira (support.atlassian.com)
Monitor and audit activity in your organization (support.atlassian.com)

FAQ

Does any data leave my instance?

No. The app runs on Atlassian Forge inside your own tenant with zero external egress, which makes it eligible for Atlassian's Runs on Atlassian trust marker.

How is it billed?

Through the Atlassian Marketplace, on your existing Atlassian bill, priced per user like any Cloud app. The listing has a free evaluation and the exact calculator for your tier.

Where do I get support?

Email support@llmgraph.ai or open an issue from the documentation page. You talk directly to the people who build the app.

Install Compliance Log Vault in about a minute.

Free evaluation from the Marketplace listing. If it does not fit your workflow, tell us what would and we will build it.

Try it free Read the deep-dive