Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

ticket: authorize legacy ticket field removal

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-08 21:17:56 +09:00
parent 2a6b9162d4
commit 51adf011b6
No known key found for this signature in database
2 changed files with 18 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.yoi/tickets/open/20260608-103842-remove-legacy-ticket-schema-fields/item.md
View File

@ -8,7 +8,7 @@ priority: 'P1'
labels: ['ticket', 'schema', 'migration', 'cleanup']
workflow_state: 'inprogress'
created_at: '2026-06-08T10:38:42Z'
updated_at: '2026-06-08T12:13:26Z'
updated_at: '2026-06-08T12:17:50Z'
assignee: null
legacy_ticket: null
queued_by: 'workspace-panel'

17
.yoi/tickets/open/20260608-103842-remove-legacy-ticket-schema-fields/thread.md
View File

@ -176,3 +176,20 @@ Needed decision before implementation continues:
No merge, close, or implementation edits have occurred.
---
<!-- event: decision author: orchestrator at: 2026-06-08T12:17:50Z -->
## Decision
Human decision received: delete `legacy_ticket` values even when non-null.
Policy for this Ticket:
- Treat existing non-null `legacy_ticket` frontmatter values as obsolete migration breadcrumbs rather than current relation authority.
- Remove `legacy_ticket` from all current local Ticket `item.md` frontmatter, including closed historical Tickets and open Tickets.
- Do not add a replacement generic external issue field in this Ticket.
- Continue to keep historical thread/resolution prose intact unless a test fixture requires a narrow update.
- The separate `typed-ticket-relation-metadata` Ticket remains the place to design durable typed relations if needed later.
This resolves the implementation block and authorizes Coder to continue the schema cleanup.
---