Ticket moves and completion reports
The idea
The runtime moves the source ticket at the events that the team's workflow names, never back or sideways. It posts one template report (outcome, evidence, caveats, what needs a person) to each place that asked.
- The problem
- Tickets moved outside the team's workflow, and people had to open the platform to see outcomes.
- Why it matters
- Tickets follow the team's process, and the outcome reaches the place the request came from, once.
- Where it stands
- In production as of
A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.