Automation rules
Automation rules (a Pro feature) keep the busywork out of your tracker: label incoming bugs, nudge stale issues, assign, move, comment or call a webhook — all from a structured builder, no scripting.
When / If / Then
A rule is a trigger, optional conditions, and one or more actions:
- When —
issue.created,issue.status_changed,issue.assigned,issue.comment_added,issue.blocked, orissue.stale(with a days-without-update threshold). - If — category, label, minimum priority, unassigned.
- Then — add a label, assign, move to a state, add a comment, or notify a webhook.
Rules can be scoped to specific teams or apply workspace-wide, and toggled on and off without deleting them.
Dry-run preview
The builder's preview runs your conditions against the live workspace before you save: how many issues match, a sample of them, and honest caveats (a preview evaluates current state, not the state at event time). No actions are executed. The same rules engine writes each automated action into the issue's activity trail, so nothing happens invisibly.
Inbound GitHub webhook
Rilbo accepts GitHub webhook deliveries (also Pro, part of automation): point a repository webhook at your Rilbo server and pull-request events move linked issues — opening a PR that references ENG-42 can move it to In Review, merging it can move it to Done. Deliveries are verified with an HMAC secret you configure in Admin; per-team state mappings are configurable over the API.
Outbound, the notify_webhook action and webhook notification channel POST JSON to any URL you give them — see configuration for channels, digests and quiet hours.