Jira Service Management · Notification Log for JSM
Every outgoing customer notification recorded as it fires, retained and exportable. Runs entirely on Atlassian.
Runs entirely on Atlassian Forge inside your own tenant. No external servers, no data egress.
A customer says "I never got the notification." JSM cannot help you: it keeps no queryable log of what it sent, and the native email log records only failed sends. Proving a notification went out is guesswork.
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:servicedesk-request | request and desk context per event |
| read:jira-work / read:jira-user | actor and recipient details |
| storage:app | the log itself, in your tenant |
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.
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.
Email support@llmgraph.ai or open an issue from the documentation page. You talk directly to the people who build the app.
Free evaluation from the Marketplace listing. If it does not fit your workflow, tell us what would and we will build it.