Data Handling and Security
Audit 360 for Jira is designed for read-only audit workflows.
Read-Only Posture
The app does not modify Jira issues, work items, custom fields, screens, workflows, filters, boards, dashboards, projects, or Automation rules as part of audit workflows.
Durable Results
Audit 360 stores summarized audit results and run metadata so administrators can load completed runs later. Durable results avoid storing:
- Raw Jira API payloads.
- Issue or work item keys.
- Credentials.
- Secrets.
- Uploaded Automation JSON.
- Raw Automation rule objects.
Temporary processing data may be used while a job runs, such as uploaded Automation JSON chunks, but durable results are summarized.
Attribution
Where run attribution is available, durable metadata stores stable account identifiers. Display names and avatars may be fetched when displayed and are not stored as durable profile payloads.
Administrator Review
Audit results are evidence for administrator review. Confirm business context, ownership, and risk before changing Jira configuration outside Audit 360.