keelapps/Digest
For people who want the week's changes, not every event
Six emails about one issue, folded into one summary.
Jira notifies per event: one issue is commented on three times, changes status twice and mentions you once, and you have six emails. Digest folds everything that changed in a period into one structured summary — grouped how you choose, delivered to an in-app inbox, read when you choose. It never filters, rewrites or intercepts Jira's own notifications.
Jira's personal notification settings can silence email, but only event by event — there is no native way to ask for “everything that changed against this JQL, once a week, in my time zone”. The usual workaround is a reporting suite: dashboards, gadgets, sometimes an external server, when all that was wanted was a summary that arrives on its own.
What it does
One subscription, one summary
Pick a JQL query, a cadence — daily at your own hour, or weekly on a chosen day — a time zone and a grouping. From then on, each period folds into a single digest.
Everything that changed, classified
Issues created, status transitions, assignments to you, priority changes, and comments that @mention you — each listed once, grouped by project, assignee or status.
See only what you may see
Digests are re-filtered against your own permissions the moment you open them. Anything you cannot see is stripped and counted — the check fails closed, never leaks.
Honest about silence
A period with no changes delivers nothing, unless you ask for empty digests. Broken JQL pauses the subscription and shows Jira's own error message rather than failing silently.
Truncates honestly
When more than 50 issues changed, the digest shows the 50 most notable and says “and N more”, with a deep link that opens the full result in the issue navigator.
Runs entirely on Atlassian infrastructure
Built on Forge with read-only Jira scopes and no external calls. The app cannot change an issue and cannot send your data anywhere.
The Monday-morning status summary, end to end
-
Subscribe once
One JQL query for the team's project, weekly on Monday at 08:00 in your own time zone, grouped by status.
-
The week rolls itself up
Each run covers the window since the last successful one — created, moved, assigned, mentioned — so a late run covers the gap instead of dropping it.
-
Open the inbox before standup
What reached Done, what is stuck, who was assigned what, where you were mentioned — one page instead of a week of emails, read before anyone asks.
-
Everyone reads their own version
A digest re-filters itself against each reader's permissions when opened. Entries a reader may not see are stripped and counted, never leaked.
Against what you have today
| Question | Jira notifications | Reporting suites | Digest |
|---|---|---|---|
| One issue changes six times in a week? | Six emails | Not addressed | One entry |
| Everything that changed against a JQL, as one list? | Not supported | A dashboard you go and check | Delivered |
| Your own cadence, your own time zone? | As events happen | Whenever you look | Per subscription |
| Comments that @mention you, called out? | One email each | Not tracked | Own category |
| A quiet week — deliberate or broken? | Cannot tell | Cannot tell | Counted |
| Does issue data leave Atlassian? | No | Often — external servers | Never |
Availability
Digest is live on the Atlassian Marketplace. It is built and deployed on Atlassian Forge and installs into your Jira Cloud site straight from the listing.
Licensing is handled by Atlassian. One subscription is free forever, with every cadence and every grouping; a paid license raises the limit to 25 subscriptions per person. Sites with 10 users or fewer pay nothing at all.
Questions, bug reports and feature requests: raise a support request.
Found a security issue? Please report it privately rather than in a public channel.