Allow removing workflow start triggers from their owning configuration #1487

Closed
opened 2026-10-27 13:40:36 +00:00 by sam · 0 comments
Owner

Workflow settings display event bindings, built-in issue routes, playbooks and workflow handoffs together, but most entries provide no way to change or remove their start relationship. Event bindings need a remove action; references to other workflows and playbooks need an editing path. Verify each displayed trigger has a working explanation or editing action and removed bindings stop appearing.

Notes

Event bindings can now be removed from Starts when with confirmation; verified through browser and persisted CRUD. Source and mapping remain intact. Upstream workflow/playbook links now open their editors. Built-in issue-label routing remains static, clearly marked Built-in; making that routing removable remains outstanding.

Close reason

All displayed starts now have a working explanation or edit path: event bindings and schedules open editors with confirmation-guarded remove (TriggerSettings.vue:30-37, BindEvent.vue:353), upstream workflow/playbook references link to their editors (TriggerSettings.vue:44), and built-in issue-label routing is a fixed server default (internal/domain/workflow/routing.go:10-21) shown as Built-in with a tooltip explaining that disabling the workflow stops it — making it removable would need a new server setting the ticket did not ask for.


Imported from beads archie-core-oc6h5 · GitHub #1717 · type bug · priority P2 · created 2026-10-15 · closed 2026-10-27

Workflow settings display event bindings, built-in issue routes, playbooks and workflow handoffs together, but most entries provide no way to change or remove their start relationship. Event bindings need a remove action; references to other workflows and playbooks need an editing path. Verify each displayed trigger has a working explanation or editing action and removed bindings stop appearing. ### Notes Event bindings can now be removed from Starts when with confirmation; verified through browser and persisted CRUD. Source and mapping remain intact. Upstream workflow/playbook links now open their editors. Built-in issue-label routing remains static, clearly marked Built-in; making that routing removable remains outstanding. ### Close reason All displayed starts now have a working explanation or edit path: event bindings and schedules open editors with confirmation-guarded remove (TriggerSettings.vue:30-37, BindEvent.vue:353), upstream workflow/playbook references link to their editors (TriggerSettings.vue:44), and built-in issue-label routing is a fixed server default (internal/domain/workflow/routing.go:10-21) shown as Built-in with a tooltip explaining that disabling the workflow stops it — making it removable would need a new server setting the ticket did not ask for. --- _Imported from beads `archie-core-oc6h5` · GitHub #1717 · type bug · priority P2 · created 2026-10-15 · closed 2026-10-27_
sam added the mediumbug labels 2026-10-27 13:40:36 +00:00
sam self-assigned this 2026-10-27 13:40:36 +00:00
sam closed this issue 2026-10-27 13:40:36 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1487