issue --json: read closure data on Linear #669

Closed
opened 2026-10-01 21:15:41 +00:00 by claude · 1 comment
Member

Found during IW-651 (analysis). Deferred by Michal on 2026-10-01. Until this is done, iw issue <id> --json prints closure: {"kind": "notImplemented"} for this tracker. Forgejo implementation and closure rules: core/model/IssueState.scala, project-management/issues/IW-651/analysis.md.

state from state.type; a linked PR is an Attachment whose metadata is integration-specific, with no promised state or merge time. Check a real attachment before design; same mapping as YouTrack (merged → mergedPullRequest, none → unknown). From vendor documentation only, not tested.

Found during IW-651 (analysis). Deferred by Michal on 2026-10-01. Until this is done, `iw issue <id> --json` prints `closure: {"kind": "notImplemented"}` for this tracker. Forgejo implementation and closure rules: `core/model/IssueState.scala`, `project-management/issues/IW-651/analysis.md`. `state` from `state.type`; a linked PR is an `Attachment` whose `metadata` is integration-specific, with no promised state or merge time. Check a real attachment before design; same mapping as YouTrack (merged → `mergedPullRequest`, none → `unknown`). From vendor documentation only, not tested.
Author
Member

Grouped into #668: "issue --json: read closure data on YouTrack and Linear". This issue is one item of that change, listed there with its evidence (follow-ups rule, iterative-works/dev-docs #432).

Grouped into #668: "issue --json: read closure data on YouTrack and Linear". This issue is one item of that change, listed there with its evidence (follow-ups rule, iterative-works/dev-docs #432).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
iterative-works/iw-cli#669
No description provided.