Jira Service Management · Notification Log for JSM

Keep a record of every outgoing JSM customer notification

Every outgoing customer notification recorded as it fires, retained and exportable. 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: JSDCLOUD-4698, "Provide an outgoing email log", with 1,490 votes. We wrote up the problem and the native workarounds on Atlassian Community.

The gap

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.

What it does

Records every outgoing notification event: request created, public reply, status change.
Captures the request, service desk, actor, and recipient set per notification.
Search and filter by request, desk, audience, and type.
Retains history for a configurable window, then prunes automatically.
One-click, audit-ready CSV export of the full log.

The log: every notification-triggering event with its recipient set.

Filter by request, desk, audience, or event type.

Events are recorded as they fire and deduplicated by id.

60-second walkthrough

Honest about its limits

Capture starts at install; events before the first sync are not recoverable.
The app records that a notification-triggering event fired and who the recipients were. Final mail delivery happens inside Atlassian's pipeline, beyond what any tenant app can observe.
Where Jira provides only an account id and no display name, the log shows the id. That is a privacy-respecting API behavior, not a bug.
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: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

The native feature it builds on

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

View customer notification logs (support.atlassian.com)
Set up notifications for your customers and team (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 Notification Log for JSM 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