Inspiration
Following up on a Jira issue usually means one person remembering to ask another one again. We read the reviews of the most installed reminder app on the Marketplace (3,427 installs and 3.5 stars when we measured it on November 3, 2026) and of the paid alternatives, and the same requests came back: remind someone other than myself, pick an exact time and not AM/PM in 30-minute steps, get a notification inside Jira and not only an e-mail, see the issue key in the e-mail subject, and one place that lists my reminders.
What it does
Teammate Reminders for Jira adds a Reminders panel to every issue.
- Remind me, the assignee, the reporter, the watchers and up to 20 teammates, at an exact date and 24-hour time. Shortcuts such as Today 17:00 and Next Monday 09:00 fill the fields in one click.
- Recipients are resolved when the reminder is sent, so if the issue changed hands the new assignee gets it.
- Delivery is a choice: a private e-mail from Jira, or a comment that @mentions the recipients (bell and e-mail). The subject reads "Reminder: KEY: your note (summary)".
- A reminder goes out once or repeats every day, every weekday (Monday to Friday in your time zone), every week or every month. A reminder set for the 31st uses the last day of shorter months.
- "Skip if the issue is already done" sends nothing for a finished issue.
- Apps > My reminders lists what you created, the next one to go out first, with snooze (1 day or 1 week) and cancel, and a history of what was sent.
- When a reminder is not delivered the status says why, for example "not sent: nobody to notify" for an issue without assignee.
- A Jira admin page limits the app to chosen projects.
How we built it
A Forge app for Jira Cloud with UI Kit: jira:issuePanel, jira:globalPage and jira:adminPage, one scheduled trigger every 5 minutes that sends what is due, and one weekly trigger for personal data reporting. Reminders are a Forge storage (KVS) custom entity indexed by due time, by creator and by issue. Sending uses the Jira REST API: the issue notify endpoint for the private e-mail, or a comment with ADF mentions. An issue that fails is retried 5 times and then marked failed, so it never blocks the queue. Validation and the date arithmetic (weekdays, month ends, time zones) are a pure module covered by 29 node:test tests. The app is Runs on Atlassian: Forge storage only, no remote backend, no egress. Five scopes: read:jira-work, write:jira-work, read:jira-user, storage:app and report:personal-data.
Challenges we ran into
Jira's notification e-mail does not show a body, so the note has to travel in the subject, next to the issue key. Monthly repeats needed a rule for the 31st that goes back to the 31st after a short month instead of drifting to the 28th. And a reminder whose recipients no longer exist must say so instead of looking sent, which is where the status wording came from.
Accomplishments that we're proud of
The app was created on November 3, 2026, during Codegeist, and Atlassian approved it for the Marketplace on November 16, 2026 after the app review, the security questionnaire and the Privacy & Security tab. It is live at https://marketplace.atlassian.com/apps/2781565032/teammate-reminders-for-jira and free for up to 10 users.
What we learned
A reminder is addressed to a role on the issue, not to a person. Resolving "assignee" at send time, and not when the reminder is created, is what makes a follow-up survive a handover.
What's next for Teammate Reminders for Jira
Reminders from a JQL filter (every issue due this week), a Rovo agent action that answers "what did I ask people to follow up on", and delivery to Jira Service Management request participants.