Notification Digest for Jira — Documentation

Last updated: 24 August 2026. Applies to the Notification Digest for Jira Cloud app.

Notification Digest bundles the updates on the Jira issues you are involved in into a single summary email instead of one email per change. It is an Atlassian Forge app: everything runs on Atlassian infrastructure and the digest is delivered through Jira's own notification system.

Requirements

• Jira Cloud. The app is not available for Jira Server or Data Center.
• A Jira site administrator installs the app; after that, every user configures their own digest — no project or admin configuration is needed.
• This is a paid app with a single tier; every feature described here is included. Your subscription comes from the Atlassian Marketplace; the app reads the licence status from Atlassian and does not store it.

Installation

1. Install from the Atlassian Marketplace listing, or from inside Jira: gear icon → Apps → Explore more apps, search for Notification Digest and install it.
2. Approve the requested permissions when Jira asks. Installed apps and their permissions can be reviewed later under gear icon → Apps → Manage apps.
3. Subscribe through the Atlassian Marketplace. There is one tier; there is nothing to choose.

Where to find it

The app adds a global page called Notification Digest. Open it from the Apps menu in the Jira top navigation. The page is personal: each user sees and changes only their own digest settings.

Using Notification Digest

1. Open Apps → Notification Digest. The page shows your current plan, your digest frequency, and which features your plan includes.
2. Use the Send me a digest toggle to switch your digest on or off, then press Save. Saving also adds you to (or removes you from) the schedule.
3. From then on the digest runs automatically — no further action is needed. Jira triggers the daily job once per day and the weekly job once per week; Forge decides the exact moment within that interval.
4. Each run looks at issues where you are the assignee, reporter or watcher and that were updated since your previous digest, and summarises per issue what changed: status transitions, assignee changes, and the number and authors of new comments.
5. Before an issue is added to your digest, the app re-checks with Jira that you can still browse it. Issues in projects you have left are therefore left out, even if you are still listed as reporter or watcher on them.
6. The summary arrives as one email via Jira's own notification system. If nothing changed in the window, no email is sent — but the window still moves forward, so you never receive the same update twice.

The digest is daily. A weekly frequency exists in the app but is not currently offered: it was built for a second edition that has not been released, so every installation resolves to the daily tier.

Access and testing

This section is for anyone who needs to verify the app rather than use it day to day — an Atlassian reviewer, or an administrator evaluating it before rolling it out.

Getting in. No account, credentials or sign-up on our side are needed, and there is no separate portal. Everything the app does happens inside Jira. Install it on a Jira Cloud site, then open Apps in the Jira top navigation and choose Notification Digest. The page opens for the logged-in user; there is no admin console and no per-project setup.

Licence. This is a paid app. The app reads the subscription from the Atlassian licence — a Marketplace evaluation licence is enough, and the app does not check anything else. There is a single tier, so no edition needs to be selected or simulated.

What you can verify immediately:

1. Open Apps → Notification Digest. The page loads and shows your current plan and the features that plan includes.
2. Switch Send me a digest on and press Save. Reload the page: the toggle is still on, which confirms the preference was stored per user.
3. Switch it off, save, and reload again. The setting is personal — a second user on the same site sees only their own state.

Seeing a real digest, without waiting for the schedule. The settings page has a Send me a digest now button under Try it now. It runs exactly the same routine the scheduled job runs — same licence check, same edition rules, same per-issue permission re-check — for you, immediately, and mails you the result through Jira's notification system.

To see a digest with content in it:

1. Change something on an issue where you are the assignee, reporter or watcher: move its status, reassign it, or add a comment.
2. Open Apps → Notification Digest and press Send me a digest now.
3. The page reports what happened — how many issues the digest covers and since when — and the email arrives in your Jira notifications.

Two things worth knowing about that button. It does not use up your next scheduled digest: it deliberately leaves your digest window where it was, so pressing it is repeatable and the scheduled run still covers the same period. And if nothing has changed since your last digest it sends no email — that is correct behaviour, and the page says so in words rather than leaving you guessing. There is a one-minute floor between sends.

What still cannot be pinned down. The scheduled delivery itself runs once per day (or once per week) and Forge chooses the exact moment within that interval; it cannot be fixed to a clock time. That affects when an unattended digest lands, not whether you can see the app work — for that, use the button above.

Permissions the app asks for — five scopes, each with one job: read:jira-work to find the issues you are involved in and what changed on them, read:jira-user for the user fields embedded in those issues (assignee, comment author), write:jira-work to send the digest through Jira's own notification endpoint, storage:app for your stored preference and the window marker, and read:permission:jira to re-check that you may still browse an issue before it is added to your digest. There is no external block in the manifest, so the app makes no outbound network call at all: nothing leaves Atlassian infrastructure.

Limitations

• Scheduled jobs cannot be pinned to an exact clock time; Forge distributes the run within the daily or weekly interval.
• In this version the settings page exposes the on/off toggle. Frequency defaults to daily, and the event and project filters that the stored preferences support are not yet editable from the UI.
• The settings page also lists features that are not implemented yet — custom delivery times, JQL and project filters, multiple digests per day, mute rules, and Slack/Teams delivery. Do not rely on them; the only edition-dependent behaviour that the app currently performs is the weekly digest frequency.
• Involvement is based on assignee, reporter and watcher. Being @mentioned is not a JQL- searchable condition and therefore does not by itself trigger a digest entry.
• Comments are reported as a count plus the authors' names, not as rendered comment text.
• A digest covers at most 200 issues per user per run (50 issues over 4 pages).
• Because Jira's notification endpoint is anchored to an issue, the email is technically sent in the context of the most recently updated issue in your digest; the other issues are listed in the body.
• Scheduled runs are not retried by Forge. If a run fails for you, the app leaves your window open so the next run covers it.
• If that visibility check cannot be completed for a run, the app sends you no digest for that run rather than an unchecked one. Your window stays open, so the next run still covers the period.

Support

Questions, bug reports and feature requests: info@kyc-checks.nl.