Blog · 28 September 2026

Jira reminder: three ways to get nudged, and which one fits

There is no Jira reminder button. Jira Cloud will not let you click an issue and say "ping me about this on Friday". What it offers instead are three mechanisms that each cover part of the job: a filter subscription that emails you a list on a schedule, a Jira Automation rule with a scheduled trigger that can comment on, notify about or change the issues a query finds, and a recurring issue that simply appears in the backlog when the thing is due again. Which one you want depends on a single question: is the reminder about work that already exists, or about work that has to happen again?

This guide goes through all three, in the order most teams should try them. Everything said about Jira Automation and the built-in features is as of September 2026, from Atlassian's own documentation.

What a Jira reminder can mean #

People search for "Jira reminder" when they mean quite different things. Sorting yours into one of these rows saves most of the effort.

The last row is the one Jira handles worst. A single one-off nudge has no native home, so the honest answer is a due date on the issue and one of the list-based methods below catching it.

Method 1: a filter subscription (free, built in) #

A filter subscription is the oldest reminder in Jira and still the simplest. You write a search, save it as a filter, and ask Jira to email you the results on a schedule. Atlassian's own description:

Subscribing to a filter provides you with a periodic notification for all work items returned by the search.

How to set it up #

1. Open the issue search and write the query. For a due-date reminder, something like assignee = currentUser() AND due <= 7d AND statusCategory != Done.
2. Save the search as a filter.
3. Run the filter, select Details next to its name, then New subscription.
4. Pick the recipients and the schedule. Choose Advanced if the simple options are not enough and write a cron expression; our Jira cron expression guide covers the syntax.
5. Select Subscribe.

What to know before relying on it #

• Only the first 200 results are sent. Atlassian's page says so directly. A reminder about a large backlog is silently cut off at that point.
• Results are per recipient. If the query uses currentUser(), each person on the subscription gets their own list, which is exactly what you want for "my due items".
• Group subscriptions need a permission. You can only pick a group you belong to, and you need the Manage Group Filter Subscriptions global permission.
• It is email only. The subscription tells people; it never changes anything in Jira.

This method is the right one for most personal "what is due" reminders, and it costs nothing.

Method 2: a Jira Automation rule on a schedule #

When the reminder should do something (post a comment that mentions the assignee, send a Slack message, bump a priority, add a label), a filter subscription is not enough, and Jira Automation takes over. The Scheduled trigger is described in Atlassian's trigger reference like this, as of September 2026:

You can run the flow at a fixed rate (for example, every 7 days), or use a Cron expression for more complex schedules. You can also choose to enter a JQL query. If you do, actions in this flow will execute on the work items included in the query.

A typical reminder rule #

1. Go to Automation in the project settings and create a rule.
2. Choose the Scheduled trigger, set it to run daily, and attach a JQL query such as due = 1d AND statusCategory != Done.
3. Add a Comment on work item action that mentions {{issue.assignee}} and says the item is due tomorrow. Mentions produce a notification, which is the nudge.
4. Optionally add a Send Slack message or Send email action for teams that do not read Jira notifications.
5. Turn the rule on and check its audit log after the first run.

We walk six complete rules of this kind in Jira automation examples.

The costs of doing it this way #

• Runs count toward your Automation usage. Each plan has a monthly allowance, and a rule that runs every day against a query spends from it. The details are in Jira Automation pricing and Jira Cloud automation limits.
• A failing rule switches itself off. Atlassian's page states that "Scheduled flows that reach a Failure status for 10 consecutive executions will disable automatically." A reminder rule that has quietly disabled itself looks exactly like a week with nothing due, so check the audit log now and then.
• Somebody has to own the rule. Rules live in project or global settings, and whoever edits them needs admin rights there.

Method 3: a recurring issue for work that comes back #

Many "reminders" are really routine work in disguise: rotate the on-call schedule, review access every quarter, send the monthly report, check the backups. For those, a reminder that points at an existing issue has nothing to point at, because the issue for this cycle does not exist yet. The cleaner fix is to have the issue itself appear on the day it is due. The ticket in the backlog is the reminder, with an assignee, a due date and a history of every previous cycle.

You can do this by hand (clone last month's ticket), with Jira Automation (a Scheduled trigger with a Create work item action), or with a scheduling app. We compared all three in Jira recurring tasks.

How it looks in Recurring Work Items for Jira #

Recurring Work Items for Jira is our app, and this is the job it was built for. You write a rule once in one project: a schedule plus an issue template.

1. Turn the app on for the project and choose who may schedule.
2. Create a rule and pick the schedule: every day, chosen weekdays, a date each month, or a weekday such as the last Friday of the month.
3. Fill in the template: summary, assignee, reporter, priority, labels. Titles can carry dates through tokens, so each cycle's ticket is named for its own period.
4. Set the due date as an offset from the run, for example the day it is created or a few days after. The app stores it as an expression, so each issue gets its own due date rather than the same fixed date forever.
5. Save. The rule's next runs are listed on the same screen.

Because it is a Forge app with its own scheduler, it consumes no Jira Automation quota. Every run, whether created, skipped or failed, is written to the rule's history with a reason, so a rule that stopped working does not look the same as a quiet week. It is free for up to 10 users.

Pair it with Method 1 and you have both halves: the recurring issue appears on time, and a filter subscription on due <= 1d nudges whoever owns it.

Comparing the three side by side #

When the simple way is enough #

You do not need a rule or an app for every nudge. Stay with the built-in options when:

• You only need a personal daily list. One filter subscription on your own due items does it.
• The reminder is one-off. Put a due date on the issue, or put it in your calendar. Building a rule for a single Friday is more setup than the reminder is worth.
• The team already lives in a chat tool and one Automation rule posting there covers every case you have.

Reach for a recurring issue when the same piece of work keeps coming back and people keep forgetting to create it. That is the point where a reminder about the work stops being enough and you want the work itself on the board.

Frequently asked #

Can Jira send a reminder before a due date? Yes, but not by default. Use a filter subscription on a query such as due <= 2d AND statusCategory != Done, or an Automation rule with a Scheduled trigger and the same JQL.

Can I set a reminder on a single issue? Not natively. Give the issue a due date and let a subscription or a rule catch it, or watch the issue if you only want to hear when it changes.

Why did my reminder rule stop? Check the rule's audit log. A scheduled rule that fails ten times in a row switches itself off, and the monthly usage allowance can also run out.

Want the routine work to show up on its own? Install Recurring Work Items for Jira and write your first rule.