Reminder Experience
See How Reminders Appear to Your Team
Once a reminder is active, Worklog Reminder automatically monitors your selected users or groups and notifies them whenever their worklogs don’t meet the defined policy.
🧭 Choosing the Right Reminder Type
Before you configure a new reminder, decide where you want users to see it and how strong the nudge should be. Use the table below to compare each reminder type and pick the one that best fits your team and policy.
🔍 Compare reminder types
🚩 In-Product Flag
Banner inside Jira, on issue view
Gentle, contextual nudge
Everyday use, teams working mainly in Jira
None beyond the app
🔁 Redirect
Banner in Jira + auto-redirect to timesheet
Strong, action-driven push
Strict compliance, billing-critical or audit scenarios
None beyond the app
✉️ Jira Email Notification
Standard Jira email in the user’s inbox
Simple, reliable notification
Orgs relying on Jira’s built-in mail & compliance model
Jira’s native notification system
📨 App Email (Worklog Mail)
Rich, structured email from Worklog Reminder
Detailed, highly informative
Teams relying on email and needing clear, self-contained info
Worklog Reminder Mail configuration
Use flags or redirects for in-product nudges, and Jira or App email when you need reliable inbox delivery.
🚩 In-Product Flag
Flags are gentle, contextual reminders that appear inside Jira while the user is working — for example, when they open or browse an issue.
When it appears: Whenever a user interacts with an issue (opens, views, or edits it), the app automatically checks whether their recent worklogs meet the active reminder policy. If the defined rule isn’t satisfied — for instance, the user logged fewer hours than required during the reporting window — a reminder flag appears at the top of the screen.
What the user sees: The flag clearly summarises which policy triggered the reminder, the reporting period it refers to, and how much work is still missing. A link to “My Reminders” leads directly to the app’s page, where users can review all active reminders and take the necessary actions to resolve them.
Frequency and behaviour: To prevent notification fatigue, each reminder flag is displayed up to three times. After the third appearance, the flag is marked as exhausted and no longer shown, unless a new reminder cycle starts once the user becomes compliant again.
Purpose: Flags deliver non-intrusive, real-time accountability. They help users stay aware of missing worklogs and fix them promptly — without disrupting their regular Jira workflow.
🔁 Redirect Action
Redirects provide a stronger nudge by taking users straight to the right page.
When it happens: When a policy is violated and the selected reminder action is Redirect, the app displays an informational banner inside Jira. The banner explains the missing time and clarifies that the user needs to complete their worklog.
After a short delay, the user is automatically redirected in a new browser tab to a predefined Jira page — usually their personal time tracking or timesheet view — where they can update their entries.
What the user experiences:
The banner appears briefly, describing the missing time and the required action.
A new browser tab then opens, taking the user directly to the correct screen for adding worklogs.
Purpose: Redirects make compliance effortless — users immediately see what’s missing and are guided to the exact place to fix it. They’re ideal for teams where accurate and timely time logging is essential for reporting, billing, or audit accuracy.
✉️ Jira Email Notification
When a reminder uses the Jira email action, the app triggers a standard Jira notification for a selected issue and user. The notification is tied to the issue context, so the user can jump straight into Jira to review and update their worklogs.
What the user receives: The user gets an email from Jira that indicates that their worklogs problem and a need attention for a given period.
Purpose: Jira email notifications use Jira’s built-in delivery channel, so reminder messages follow the same security, compliance, and audit rules as your existing Jira emails. This is especially useful for organisations with strict IT policies, because no additional email infrastructure is required and all communication stays inside your Jira environment.
📨 App Email (Worklog Reminder mail)
App email uses Worklog Reminder’s own email template to send rich, structured reminders to users.
When it’s used: When a policy is configured with the App email action and the mail integration is set up by an administrator, the app sends a dedicated reminder email whenever a check finds missing hours.
What the user sees: Each email includes:
A clear headline stating that their logged hours need attention
The policy name and reporting window
A breakdown of required, logged, and remaining time
A progress indication toward the target
Recommended next actions and a link back to Jira to update worklogs
This gives users a complete, self-contained summary of what’s missing and how to fix it — without needing extra explanations from managers.
Purpose: App emails are ideal when you want professional, consistent reminder emails that highlight the policy, numbers, and next steps in one place. They work especially well for teams that rely on email for daily communication or need a more structured reminder format than a simple Jira comment.
To use App email, make sure Worklog Reminder Mail is configured in Jira admin settings.
🧭 Choosing the Right Experience
Each reminder type fits a different communication style:
Flag → Subtle and contextual. Ideal for everyday, in-product nudges.
Redirect → Strong and immediate. Perfect for strict compliance environments.
Jira email → Simple and reliable. Uses standard Jira notifications via issue comments.
App email → Rich and structured. Best when you want detailed summaries with clear next steps delivered straight to the inbox.
You can mix and match reminder types across different policies to suit various teams, projects, or working styles.
💡 Preview Before You Launch
In the reminder configuration panel, use Preview experience to test your setup before activating it for everyone. You’ll see the exact text, tone, and placement that users will experience when a reminder triggers.
This lets you adjust your wording and confirm visibility before launching the policy live.
▶️ Next: View Compliance & Results
Once reminders are running, learn how to review compliance reports, track upcoming executions, and understand which users have resolved or ignored their notifications.
Last updated