Auto Assign for Redmine · RedminePRO Docs

Q: The wrong rule fired.

A rule naming the tracker beats one for All trackers. Look for a more specific rule on the same status.

When an issue reaches a status, hand it to the right person automatically. "A bug moves to testing, the QA lead picks it up", without anyone having to remember. Rules live per project, or in named sets you attach to many projects at once so one edit changes them everywhere.

A rule never overrules a person. If the same change that moved the status also set an assignee by hand, the manual choice stands.

What you can do

Availability: Business and above.
Turn it on: Per project: Project → Settings → Modules → tick Auto Assign. An Auto assign entry then appears in the project menu for whoever holds the permission below.
Permissions: Nobody needs a permission for rules to apply. They are part of how the project works, not something a person invokes.
Settings: None workspace-wide. Everything is configured per project, or in the shared rule sets at Administration → Auto assign.
Using it: Enable the module on the project and open Auto assign in its menu. Add a rule: pick a tracker (or All trackers), the status that triggers it, and Assign to.

Rules for one project — From a live RedminePRO workspace.

Configure

Settings, permissions, modules and how to use it on RedminePRO Cloud.

Install on your own Redmine

Requirements, install, update and remove, for a self-hosted Redmine 6.

Common questions

Nothing was assigned.

Check the module is on for the project, that a rule matches this tracker and status, and that the same save did not also set the assignee by hand. A manual choice always wins.

The wrong rule fired.

A rule naming the tracker beats one for All trackers. Look for a more specific rule on the same status.

A project rule is being ignored.

It is not. A project rule beats an inherited one. The inherited row is marked overridden by a project rule.