Skip to content
JiraVision

Automations & the activity feed

Rule-based automations, manual runs, and the audit trail of everything that changed.

Automations & the activity feed

Automations

/dashboard/automation is where you define rules: a trigger, a condition and an action. Rules are stored rows with full CRUD through /api/automation and /api/automation/<id>, and each one can be run on demand with POST /api/automation/<id>/run so you can test it before leaving it enabled.

  1. Create the rule and give it a name that says what it does.
  2. Run it once manually and read the result.
  3. Enable it.
  4. Watch the runs on the same page — each run records what it matched and what it changed.

Automations that change tasks go through the same write path as a human edit, so they produce the same notifications and appear in the activity feed. That is deliberate: nothing should happen in this workspace without a trace.

Activity feed

/dashboard/activity lists changes across the workspace with actor, target and timestamp, backed by /api/activity and /api/activity/<id>. Use it to answer "who moved this task?" or "when did this sprint start?".

Related audit trails, each on its own page:

  • Settings writes: the audit feed card in /dashboard/settings.
  • Role changes: the audit feed in /dashboard/team/settings.
  • Marketing content edits: /api/admin/cms/audit, shown in /admin/cms.
  • Automation runs: the run log on /dashboard/automation.

Guardrails

  • An automation cannot bypass a role check. If the rule's actor lacks permission, the run fails and the failure is logged.
  • Deleting a rule keeps its historical runs, so the feed stays honest.
  • Bulk task changes are recorded once per affected task, not once per run.