Additional tracker adapters (Jira, Linear) #638

New issue

Closed

opened 2026-07-07 21:47:16 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-07 21:47:16 +00:00

Member

Parent epic: #633. Depends on: #634 (Tracker port), and best after #636 and #637 prove the port.

Context. Jira and Linear are the largest-audience trackers after the first two land. They are backlog, not launch-gating, but naming them keeps the compat surface honest and gives contributors a clear next target.

Proposed change.

A Jira Tracker adapter: issue read/comment/transition, JQL-free lookup by key, close via a configured transition. Support both Cloud and self-hosted (Data Center) base URLs.
A Linear Tracker adapter over its GraphQL API: issue read/comment/state-change, close via a configured workflow state.

Acceptance criteria.

Each adapter carries one issue end to end against a real instance.
Neither forces a change to the Tracker port. If it does, fold the change back into #634.

Note. Split into two issues if either grows its own discussion. Filed together to avoid backlog noise while both are speculative.

Milestone: foreign-stack compat. Filed from the read-only director surface (she/her), part of the release-readiness issue batch.

Parent epic: #633. **Depends on:** #634 (Tracker port), and best after #636 and #637 prove the port. **Context.** Jira and Linear are the largest-audience trackers after the first two land. They are backlog, not launch-gating, but naming them keeps the compat surface honest and gives contributors a clear next target. **Proposed change.** - A Jira `Tracker` adapter: issue read/comment/transition, JQL-free lookup by key, close via a configured transition. Support both Cloud and self-hosted (Data Center) base URLs. - A Linear `Tracker` adapter over its GraphQL API: issue read/comment/state-change, close via a configured workflow state. **Acceptance criteria.** - Each adapter carries one issue end to end against a real instance. - Neither forces a change to the Tracker port. If it does, fold the change back into #634. **Note.** Split into two issues if either grows its own discussion. Filed together to avoid backlog noise while both are speculative. --- Milestone: foreign-stack compat. Filed from the read-only director surface (she/her), part of the release-readiness issue batch.

coilyco-ops added this to the foreign-stack compat milestone

2026-07-07 21:47:16 +00:00

coilyco-ops added the

label

2026-07-07 21:47:16 +00:00

coilyco-ops referenced this issue

2026-07-07 21:47:50 +00:00

Split issueForge into a git-host port and a Tracker port #634

coilyco-ops referenced this issue

2026-07-07 21:48:40 +00:00

[epic] Release readiness = running ward on foreign stacks (split-stack: git host + tracker) #633

coilyco-ops added the