[PixPMusic]

Jira users with an existing TWG login need support for current TWG releases. This adds a Jira tracker on top of #19274 using native TWG commands, with properties and linked metadata for Jira and Linear.

• Uses jira workitem get, query, comment query/create, jira space query, and whoami. T3 uses the environment's CLI login and stores no Jira API token. Native flattened responses and issue, comment, and project pagination are handled in the adapter.
• Preserves public replies and JSM internal notes, including audience badges. Internal-note requests are refused for trackers without that capability.
• Adds a shared read-only Properties tab for Jira and Linear, with field search, empty-field filtering, and pinning to Summary. Pins use the tracker's stable issue ID and save field IDs in browser storage. Jira displays metadata field names where available, with field IDs as fallback; Linear displays priority, estimate, due date, cycle, project, team, assignee, labels, status, and timestamps. Git forges do not receive a Properties tab.
• Treats linked issues and web links as separate sections. Jira link directions, parent/sub-issues, and web links are decoded from native TWG output. Linear includes outgoing/incoming relations, parent/sub-issues, and non-PR attachments. Linked issues show their relationship and status and open inside T3 from either the Issues page or a thread panel. Web links open externally. Truncated Linear lists link to the complete list in Linear.

Validation:

• Required changed-file checks: formatting, lint, knip, generated GraphQL consistency, typechecks of 32 affected packages, and 15 focused tests.
• Earlier adapter/service tests also covered authentication without secret-store access, site bindings, audience handling, and cross-project write refusal.
• Read-only live verification with TWG 1.4.3 decoded an issue, its comments, paginated search, the environment login, and project scopes. The properties/links decoder also passed against a real native response, including named custom fields, an issue relationship, and web links.
• Browser/mobile UI and real comment writes were not exercised.

Limits: the project picker uses TWG's default Jira site. Jira field editing, creation, and status changes stay in Jira. Jira cannot search issue mentions. This PR depends on the open issue-tracking stack and targets issues/5-linear.

The old twg api command was real: Atlassian's 1.3.5 compatibility notes confirm its removal. This implementation uses current native commands.

Model: GPT-6.1 Sol, high reasoning effort | Harness: Codex in T3 Code.

[juliusmarminge]

Note

This comment is posted by Julius' dot

Leaving this open under triage:keep-open. The description says scope approval is missing, and this includes #6315's unmerged issue-tracking foundation plus Jira, unowned issue linking, and the Properties tab. Under the prior-approval rule, can a maintainer confirm whether to review these together or first agree on separate proposals?

[Bil0000]

Sry we wouldnt merge this atm

We're already finalizing some final stuff on the issues page with the current scope, we cant expand the scope rn as it will increase the time before we ship + increase the things we need to test

Will keep your PR in mind for the near future tho, thx

Pls close it

[PixPMusic]

Sry we wouldnt merge this atm

Will keep your PR in mind for the near future tho, thx

Pls close it

This PR was opened after Julius suggested rewriting your PR with a newer model.

I'll rebase it with the Jira changes once you actually get yours merged. thanks.

[Bil0000]

It was a wrong callout after I discussed it with him 😅

Working on multiple things now on my PR, its still WIP anyways

Looking forward to your follow up 🫡