Automation & watchers

Recurring ticket rules

• Project-scoped one-time, daily, weekly, monthly, and yearly rules
• Managed by administrators or roles with Manage recurring tickets
• Central and per-rule database locking to prevent duplicates
• Last run, next run, status, and concise error information

Create a recurring ticket rule

1. Enable the Redmine UX Toolkit module for the project and grant Manage recurring tickets to the responsible role. Administrators can manage all rules.
2. Open the recurring-ticket rule list and choose New recurring ticket rule.
3. Select the project, tracker, priority, optional assignee and category, then enter the subject and description.
4. Select one-time, daily, weekly, monthly, or yearly recurrence and set the next run date. Enable the rule and save it.
5. Verify the calculated next run and status in the list. A one-time rule disables itself after its issue is created successfully.

What the scheduler does

Each central run finds due enabled rules, obtains a per-rule database lock, and creates a normal Redmine issue. It records the last run, next run, status, and a concise error. Locks prevent overlapping central runs from creating duplicate tickets.

If no issue is created

• Confirm that the central scheduler has run after the rule's next-run date.
• Confirm the rule and project are enabled and that tracker, priority, assignee, and category still belong to the selected project.
• Read the rule's last status and message before moving the next-run date or retrying.

Watcher automation

Optional switches add the author when a new issue is created or add a logged-in commenter after a real non-blank comment. Both paths use Redmine's watcher logic and avoid duplicates.

• Author watching runs only when an issue is first created.
• Commenter watching runs only after a logged-in user submits non-blank notes; field-only updates are ignored.
• If Redmine does not allow the user to watch the issue, no watcher is added. Existing watcher entries are never duplicated.