Creating the same issues every month. Informing the same person after every closed issue. Remembering before every expiry date that a certificate needs renewing. Someone does that by hand, and at some point someone forgets.
The Automation plugin handles such work by rule. A rule consists of a trigger, optional conditions and one or more actions.
How it works day to day
- Choose a trigger. A rule starts on an event, for example when an issue is created or a status is set, or on a schedule.
- Set conditions. The rule only applies under certain circumstances, for example only in one project, only for one tracker or only at a certain priority.
- Define actions. Create an issue, assign it, change a status or a field, add a comment, send a notification. Several actions run one after another.
- Test it. A rule can be used in one project first, before it applies everywhere.
What changes
- Recurring issues appear reliably instead of when someone remembers.
- Dates are announced beforehand instead of noticed afterwards.
- The same manual steps after a status change disappear.
Typical rules
- Onboarding: a new employee triggers a fixed list of tasks
- Maintenance: monthly or quarterly issues per plant
- A reminder before a certificate or contract expires
- Escalation when an issue sits in a status for too long
Which functions the Redmine Automation plugin brings along and what it costs is described on the product page.