Pack: ticket-triage

Triages new and updated Redmine, JIRA and ServiceNow tickets - a cited triage draft for a person to send (L1), or a status or assignment change or a posted reply that runs only after a person approves it (L2).

Field Value
Kind automation
Version 0.1.0
Needs a credential to publish no
Okg modules it needs none
Packs it needs ops-record

In which bundles

Add it to an instance with archi add ticket-triage.

Sources

This pack has no sources.

Questions

This pack asks no questions.

Credentials

The manifest names no credential variable.

Freshness limits

The pack declares no freshness limit.

Invariants

The pack declares no invariant.

Playbooks

  • triage.md

Live tools

  • archi.tools.tickets:set_ticket_status (idempotent)
  • archi.tools.tickets:assign_ticket (idempotent)
  • archi.tools.tickets:post_reply (idempotent)

Automation

Field Value
Trigger type = ticket_queue, system = ['redmine', 'jira', 'servicenow'], queue = *
Context gate sources = ['tickets.tickets', 'jira.jira', 'servicenow.servicenow']
Playbook triage.md
Budget cost_per_run = 0.05, cost_per_day = 5, runs_per_hour = 30
Level it starts at L1
Highest level the pack allows L2

The instance sets the level in archi.yaml. A bundle can lower the upper bound but not raise it. Every automation starts in shadow mode.

Action classes

Id Mediator Reversible Highest level Blast radius
assign_ticket archi.tools.tickets:assign_ticket no L2 One ticket's assignee or assignment group and one note on it; the rollback sets it back.
draft_reply draft_reply yes L1 Nothing outside the ops record; the draft is on the proposal and nobody is sent anything.
post_reply archi.tools.tickets:post_reply no L2 One note on one ticket, visible to the person who opened it, in the ticket system the payload names.
set_ticket_status archi.tools.tickets:set_ticket_status no L2 One ticket's status and one note on it, in the ticket system the payload names; the rollback moves it back.