> For the complete documentation index, see [llms.txt](https://teranoapps.gitbook.io/missing-worklog-reminder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teranoapps.gitbook.io/missing-worklog-reminder/usage/create-worklog-reminder.md).
# Create Worklog Reminder
#### Set Up Your First Worklog Reminder in Minutes
Creating your first **Missing Worklog Reminder** takes less than five minutes.\
Follow these simple steps to configure who should receive reminders, how often they should run, and what kind of action will be triggered when someone falls behind on their worklogs.
***
#### π Where to Find the Reminders Panel
Before creating your first reminder, open your **project settings**.\
Navigate to:
**Project settings β Missing Worklog Reminder**
This section appears in the left-hand navigation menu inside your Jira project space.\
From here, administrators can view all existing reminders, create new ones, or adjust current policies.
***
**π§ Step 1: Define Applicable Users**
Start by selecting **who** the reminder applies to.\
You can target **individual users** or entire **groups**, depending on how your teams are structured.
**Applicable users**
> Select which users should fall under this reminder. You can add individual people or target entire groups.
* **Users** β Target specific people in your organisation.
* **Groups** β Apply the reminder to an entire group (e.g., Developers, Support, or QA).
Use the search bar to find and add users from your Jira directory.\
Each selected user becomes part of this reminderβs audience.
***
**β± Step 2: Define the Policy Rules**
Now that youβve chosen your audience, itβs time to define **what rule they must comply with** β and how often it will be checked.
**Constraints**
> These settings define the compliance policy. Whenever the conditions are not met, Missing Worklog Reminder automatically notifies affected users.
**Reminder window**\
Decide how frequently the app should verify that users meet their logging requirements:
* π **Daily policy** β Every workday must include the required number of logged hours.
* π
**Weekly policy** β Each week must contain enough logged workdays to meet the target threshold.
* π **Monthly policy** β The entire month is checked to confirm minimum logged hours or days.
**When the checks run**\
Each reminder policy runs its compliance check automatically **at the end of the selected time window**:
* **Daily** β at the end of each workday.
* **Weekly** β at the end of the last workday of the week.
* **Monthly** β at the end of the last workday of the month.
When the check completes, **a result entry is created for every user** covered by the policy.\
Each user can review their own reminder status and details in [**My Worklog Reminders**](/missing-worklog-reminder/usage/my-worklog-reminders.md).
**Threshold condition**\
Set the rule that defines **what βcompliantβ means** within the selected window.
You can decide whether compliance requires work logged to be:
* **More than** a defined threshold, or
* **Less than** a defined threshold (for detecting overlogging).
**Example:**
> Define a **weekly policy** requiring *at least 5 days* of logged work.\
> If a user records fewer than 5 workdays in that week, the reminder will trigger automatically at the end of the window.
Each reminder policy represents a **non-negotiable rule** β users must meet it to stay compliant.\
If they donβt, the app immediately marks the policy as violated and sends a corresponding notification (flag, redirect, Jira email, or app email), depending on your selected action type.
***
**π Step 3: Choose the Reminder Action**
Now decide **how** your users will be notified.
**Action reminder**
> Pick which reminder style will nudge people towards the right follow-up action.
You can choose one of the following options:
* π© **Flag** β Display an in-product message directly inside Jira, explaining what needs attention.
* π **Redirect** β Automatically send teammates to the time tracking page where they can fix the issue.
* βοΈ **Jira email** β Notification in a Jira issue context so they receive a Jira email notification.
* π¨ **App email** β Send a structured reminder email generated by the app, with a clear summary of the policy, reporting window, required vs logged time, and next steps.
To validate your configuration, you can use **Preview the action**.\
Run a dry-run workflow to test how the in-product message will look before launching it to your team.
Click **Run Preview** to see the sample reminder exactly as your teammates would experience it.
To use **App email**, make sure the **Worklog Reminder** integration is [configured](/missing-worklog-reminder/usage/configuration/worklog-reminder-mail.md) in Jira admin settings.
***
**β
Step 4: Create and Launch the Reminder**
Once youβve configured users, constraints, and actions, click **Create reminder**.
Your new reminder will appear in the **Reminders list**, where you can review its details and monitor future execution dates.
Each reminder entry shows:
* Reminder name and type (Daily, Weekly, Monthly)
* Applicable users or groups
* Defined thresholds
* Chosen action (Flag, Redirect, or Email)
* **Next scheduled run** β when the next compliance check will occur
From this table, you can edit, pause, or delete reminders at any time.
***
**π― What Happens Next**
After creation, the reminder runs automatically on the selected schedule.\
When users fall below the defined threshold, the chosen reminder action will trigger and guide them to correct their worklogs β no manual follow-up needed.
Your compliance checks now run on autopilot, keeping your time tracking consistent and transparent across the organisation.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://teranoapps.gitbook.io/missing-worklog-reminder/usage/create-worklog-reminder.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.