How to Set a Reminder in Jira Without Changing the Due Date

Why there is no “remind me” in Jira

Open a work item’s ⋯ menu and you will find actions such as Log work, Move, Clone, Archive and the export options — but no reminder. If you search for “jira remind me”, there is no built-in command behind it.

1 2 Enlarge Enlarge screenshot

Atlassian’s public request “Ability to set reminders on issues at a specific date/time” (JSDCLOUD-12377) was opened in 2014 and was still unresolved, under review, when checked on 2 October 2026. Until it ships, each Jira reminder is built from filters, fields or automation.

A personal follow-up list

The lightest option is a list of work items you want to come back to, emailed to you every morning. Mark the work item — watch it, or add a label such as follow-up — and save a filter:

project = SECOPS AND watcher = currentUser() AND statusCategory != Done ORDER BY updated DESC

Keep the project in the query. On the test site, the same filter without project = SECOPS returned 307 open work items — far too many to work as a jira task reminder list. With the project, it returned SECOPS-165 only. A label is more precise than watching, because you add it only to items you really want to follow up.

Save the filter, open Filter details, select Add subscription and choose Daily:

1 2 3 Enlarge Enlarge screenshot

The subscription sends email reminders as one list (up to the first 200 results) to you. It can also go to a group you belong to if you have the Manage Group Filter Subscriptions global permission. Tick Email this filter, even if there are no issues found only if an empty email is useful to you.

Check: the filter shows only your follow-ups, and the subscription is listed in Filter details.

A Follow-up date field

When the day matters, store it in its own field instead of the due date. Ask a Jira admin to add a Date picker field named “Follow-up date” to the work type (in team-managed spaces, a space admin can add fields). For the example: due date 9 October, Follow-up date 3 October.

Then save a filter of follow-ups whose day has come and subscribe to it daily, as above:

project = SECOPS AND "Follow-up date" <= endOfDay() AND statusCategory != Done ORDER BY "Follow-up date" ASC

This is a clearer follow up reminder than a label: the work item carries the date, everyone who can view the field sees it, and overdue follow up reminders stay in the list until someone acts.

Check: on the follow-up day the work item appears in the filter, and its due date still says 9 October.

An email on the follow-up date

For team-wide Jira task reminders — an email to each assignee instead of one list — build a daily automation flow on the same field. The steps are the same as for due dates in the due date reminder guide; only the query changes:

project = SECOPS AND "Follow-up date" = startOfDay() AND statusCategory != Done

Untick Only include work items that have changed since the last time this flow executed, add Send customized email to the Assignee user field, and choose Plain text: smart values work there as written (in Rich text the editor asks you to wrap them in inline code). The flow sends reminder emails one per matching work item, for example with the subject Follow up: {{issue.key}} {{issue.summary}}.

How much upkeep each method needs

Every native method needs two edits per follow-up: set the marker or date, then clear it. Thirty follow-ups this week mean thirty markers or dates to keep in order. The subscription or the flow saves you from checking Jira by hand, but it does not maintain the follow-ups for you.

What to check in a reminder app

If the native setup takes more effort than the reminders themselves, a reminder app for Jira can keep the reminder on the work item. Compare tools on the actual workflow:

• Recipients. A good reminder tool shows who gets the email before you save: you, the current assignee, named colleagues. Check whether “current assignee” is resolved when you save or when it is sent.
• Time. Does each reminder have its own date, time and time zone, or does the reminder software run on one global schedule?
• Repeats. A recurring reminder needs a clear end: an end date, and what happens when the work item is Done. Recurring reminders that never stop become noise.
• Delivery. Email reminder services should show whether a message was sent, skipped or failed.
• Scope. A task reminder app may create separate tasks; a follow up tool for Jira should keep the follow-up on the existing work item and leave the due date alone.
• Access and price. Who may receive emails, whether they need Jira access, and the price at your site’s size.

Follow-up Email Reminders, which I build, is one such follow up app: a one-time or recurring reminder on the work item for you, the current assignee or named colleagues, at a chosen date and time, without changing the due date. The reminder apps comparison lists others.

Common questions

Follow-up Email Reminders for Jira sets one-time or recurring reminders on the existing work item — for you, the current assignee or named colleagues, with a date, time and time zone — while the due date stays unchanged. It is free for teams of up to 10 users.