Atlassian · Jira Service Management Cloud
AuditPack for Jira Service Management
Collect change approvals, history and SLA outcomes into one audit pack with a gap report.
- Works with Jira Service Management Cloud
- Marketplace Atlassian Marketplace
Coming soon
Submitted to the Atlassian Marketplace for review
AuditPack for Jira Service Management was submitted to the Atlassian Marketplace on 22 October 2026 and is waiting for Atlassian’s review. It has not been approved or listed, and cannot be installed by the public yet. This page exists so the address is stable when that changes.
Coming soon toAtlassian Marketplace
What it does
AuditPack for Jira Service Management is an Atlassian Forge application that builds one evidence pack for an auditor from a Jira Service Management project and a date range. The pack covers change requests, approvals (who decided and when), status history, comments, the attachment list, linked issues and SLA outcomes. It flags gaps and exports a PDF report, a gap-report CSV and a ZIP with one CSV per evidence type, a JSON file and SHA-256 checksums. It reads from Jira, does not write to Jira, and the application stores nothing.
Capabilities
One pack from a project and a date range
Choose a service project, the date to filter on (created, resolved or last updated) and a from-to range of at most 24 months. Include change requests only or every request, and choose which issue types count as change requests; types named like “change” are preselected.
The evidence an auditor asks for
For each issue the pack holds the approvals (who decided, when), the status history, the comments with public and internal ones marked, the attachment list (file names, sizes and types, never file content), linked issues and SLA outcomes.
A gap report that shows its evidence
Six rules flag, for example, a change without an approval or an approval completed after implementation started. Each gap states the evidence it rests on. A gap is a fact to explain, not a finding of non-compliance.
PDF, CSV and ZIP with checksums
Export a PDF report, a gap-report CSV and a ZIP with one CSV per evidence type plus evidence.json, README.txt and SHA256SUMS.txt. The checksum file lists the SHA-256 of every file, and the PDF cover shows the fingerprint of evidence.json.
In each project and under Apps
AuditPack adds a page to the sidebar of each Jira Service Management project, fixed to that project, and a global page under Apps where you pick any service project you can browse.
Read-only, as the signed-in person
The app requests two read-only scopes, read:jira-work and read:servicedesk-request. Every Jira read runs as the signed-in person, so a pack contains only what that person may see. The app never reads Jira with its own identity and does not write to Jira.
The application stores nothing
No Forge storage, database, cache, scheduled jobs or queues. No external network calls, analytics, telemetry or externally hosted code or fonts. Your browser builds the files locally and saves them to your device when you download them. Atesen Software operates no server for it and cannot see your data.
Questions
Where does AuditPack for Jira Service Management run?
AuditPack is an Atlassian Forge application and runs on Atlassian (Runs on Atlassian). Atlassian hosts its code and processes its requests. Atesen Software operates no server or database for the application and has no access to customer data.
What does AuditPack for Jira Service Management connect to?
Only your Jira site. The application makes no external network calls. It has no Forge remote, no web triggers, no analytics, no telemetry and no externally hosted code or fonts; the PDF fonts ship inside the app. Every Jira read runs as the signed-in person, and the app never reads Jira with its own identity.
How do I get help with AuditPack for Jira Service Management?
Support for AuditPack for Jira Service Management is provided by email in English and Turkish.
Email support@atesensoftware.com. We aim to acknowledge every support email within two business days (Europe/Istanbul).
What we do not claim
- It has not been approved or listed on the Atlassian Marketplace and has no installation count, customer list or review history.
- It holds no security certification and has not undergone a third-party audit.
- A pack is not a substitute for the auditor’s own judgement and does not prove that a control worked. It only reflects what Jira recorded and what the person building it is allowed to read.
- A gap is a fact to explain, not a finding of non-compliance.
- A pack holds at most 1,000 issues and covers at most 24 months. Attachment contents and custom fields beyond the standard issue fields are not included.
- Jira records one completion time per approval step, not one per approver, so the pack cannot show a separate time for each approver.
- The PDF covers Latin, Latin Extended (including Turkish), Greek and Cyrillic text. Other scripts print as “?” in the PDF, while the CSV and JSON files keep the original text.
Marketplace
Atlassian Marketplace: Submitted for review on 22 October 2026 — not approved, not listed, and not installable by the public yet.
Coming soon toAtlassian Marketplace