support-request see history edit this page

Talks about: , and

What you choose

tik adopt reads these from the template itself and asks for each one, typed and validated — no EDN to hand-write.

QuestionAnswer
escalate-after:stringescalate an untriaged request after (ISO-8601, e.g. PT48H)
with-escalation:booleanflag requests nobody triaged in that window? (optional)
with-repro:booleanrequire a reproduction before a technical fix counts? (optional)
with-ack:booleanclose only once the customer confirms? (optional)

Identity

Your answers decide this one: turn a stage off and the process is a different process with a different address. The shape below is what support-request.params.edn produces, with every option on:

sha256-92c2e66b1706e37f5036fd5c3365a8c773bb1fdadb6c39286cf37aae78741bfb

Shape

Every option on. Stages that depend on an answer say so below.

● received
├─▶ triaged            ⊢ category · severity · ✎triager
│   │
│   ├─▶ reproducible   ⊢ category = technical · ⧉repro/
│   └─▶ resolved       ⊢ resolution.ref · (¬category = technical | ⤳reproducible)
│       │
│       ▼ closed ★     ⊢ customer.ack
└─▶ escalated          ⊢ ⏱PT48H · ¬category

Roles to fill

Every role ships empty, so adopting a process never inherits somebody else’s org chart. Name yours with tik roles add <role> <actor>.

Facts it records

PathShape
category[:enum :billing :technical :account :abuse]
customer.ack[:string {:min 2}]
resolution.ref[:string {:min 8}]
severity[:enum :low :normal :high :critical]

Stages

received

Reached immediately — it carries no guards.

Runbook: kb/runbooks/support-request-received.md

triaged

Follows received.

Reached when:

Runbook: kb/runbooks/support-request-triaged.md

escalated

Included when you answer yes to with-escalation.

Follows received.

Reached when:

Runbook: kb/runbooks/support-request-escalated.md

reproducible

Included when you answer yes to with-repro.

Follows triaged.

Reached when:

Runbook: kb/runbooks/support-request-reproducible.md

resolved

Follows triaged.

Reached when:

Runbook: kb/runbooks/support-request-resolved.md

closed · sticky

Included when you answer yes to with-ack.

Follows resolved.

Once reached it stays reached: the fold carries it forward, so later evidence cannot take it away.

Reached when:

Runbook: kb/runbooks/support-request-closed.md

Take it

tik adopt templates/support-request.tmpl.edn

tik adopt asks each question above at the prompt, then expands and lints the answers into a plain definition — the template never runs as code, and the expanded EDN is what your tickets pin.

Read the stages before you adopt: they say who has to sign what, which is a decision about your organisation.