OVERALL RATINGS
INSTALLS
1
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appEvery outgoing customer notification — recorded as it fires, retained and exported as audit-ready CSV
The outgoing notification log JSM never kept
Every customer-facing notification, recorded live as it fires: the request, who acted, and the recipients by display name. Not just the failures.
Search it, filter it, prove it was sent
Filter by request, service desk, audience, or type. Answer what you sent on a given request, and to whom, as a quick lookup.
Retained past JSM's window, plus CSV export
The daily rollup recomputes the digest and prunes past your retention window. The whole log exports as audit-ready CSV.
More details
JSM Notification Log is built for admins and auditors who need to prove what was communicated to customers. Runs entirely on Atlassian Forge — no external servers, no data egress, eligible for the Runs on Atlassian badge. Read-only: it records and exports, changing nothing in Jira Service Management. Free for instances up to 10 users, then a clear per-agent price with standard Atlassian volume tiers. From Katabarwa Labs — small, single-purpose governance tools that run entirely inside your tenant.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy and security questionnaire has been filled by the partner
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Notification Log for JSM integrates with your Atlassian app
Version information
Version 3.1.0•for Jira Cloud
- Release date
- Sep 10th 2026
- Summary
- Recipient display names in the log and CSV export (adds read:jira-user scope)
- Details
Recipients now appear by display name instead of raw account IDs, both in the admin view and in the CSV export. New permission: read:jira-user (read-only). It resolves the account IDs already recorded in your notification log to display names via /rest/api/3/user/bulk — no directory browsing, no writes, and no data leaves your tenant. The app remains eligible for Runs on Atlassian. Fail-soft: if name resolution is unavailable, entries still record and export with the account ID exactly as before, and no notification is dropped or delayed. Everything else is unchanged — the same live recording of every outgoing customer notification, the same retention window, the same filters and export. Your Jira admin will be asked to approve the new permission before the upgrade applies; until then you stay on 2.1.0 and the app keeps working.
- Payment model
- Paid via Atlassian
- License type
- Commercial