twg-jira

twg

twg help

CLI launcher fallback

twg <command>

command not found

$HOME/.local/bin/twg

$env:LOCALAPPDATA\Programs\twg\bin\twg.exe

Use When

• A Jira key, issue URL, project key, board, sprint, filter, or dashboard is the primary anchor.
• The user asks to create, update, transition, comment on, link, watch, or delete Jira work.
• The user asks to find or review duplicate Jira workitems.
• Required or custom fields must be discovered and populated.
• A workflow skill needs authoritative Jira fields or status.

First Route

get

search

query

rovo search --app jira

references/duplicates.md

context

jira workitem link

twg help describe "<exact path>"

Jira Semantics

• "Issue" and "workitem" refer to the same Jira object in user language.
• Jira projects/spaces are not Atlas projects. Use Jira for issue containers, schemes, boards, versions, components, filters, and dashboards.
• JSM requests have an underlying Jira workitem, but approvals, portals, queues, request types, and SLAs belong to JSM.
• Search results are candidate anchors. Use the native workitem read for final fields and status. Plain

  get

  avoids supplemental hydration; add

  --comments

  for complete comments or

  --remote-links

  for Jira remote links. The two enrichment flags may be combined. Use

  --full

  by itself for all fields and both enrichments.
• For "what should I pick next," query actual open Jira work or the requested board backlog. Do not rank from broad activity alone.

Safe Reads And Writes

• Resolve the site and workitem key before mutation.
• Read current state before update, transition, link, comment, or delete.
• Discover create/update field metadata before supplying required or custom fields.
• Use returned

  customfield_*

  IDs rather than display names in writes.
• Discover available transitions instead of guessing a transition name or ID.
  • Run

    twg jira workitem transition --id <KEY> --site <SITE> -o json

    without

    --transition-id

    to discover available transitions, their screen field requirements, and required fields.
  • Select a transition from the result and use its

    requirements

    to gather the screen-required field values before calling with

    --transition-id

    .
  • Treat required fields as user-decision inputs. If the user did not supply a required value, do not infer or choose an allowed value; ask the user before transitioning. This includes Resolution: a request to cancel does not imply

    Won't Do

    ,

    Declined

    ,

    Duplicate

    , or another Resolution.
  • This discovery call is read-only and does not transition the workitem.
• Keep global Jira field administration separate from workitem field values.
• Use typed workitem artifact links when the request is to add Jira remote links to PRs, repos, deployments, builds, branches, commits, Loom videos, or meetings. These are not Jira Software devinfo/provider writes.
• Verify mutations with a native read and report the resulting key and URL.

Handoffs

• Load

  twg-context-discovery

  for dependencies, related documents, or implementation links; load

  twg-responsibility-routing

  for owners, experts, authority, or escalation.
• Load

  twg-status-rollups

  for project, sprint, team, or leadership synthesis.
• Load

  twg-engineering-work

  when the Jira anchor must be traced to PRs or repositories.
• Load

  twg-operational-health

  for incident, PIR, or reliability workflows.

References

• references/workitems.md

  - workitem reads, writes, comments, and links

• references/fields-and-transitions.md

  - metadata-first fields and workflow changes

• references/querying.md

  - JQL and board/backlog selection

• references/duplicates.md

  - prompt driven duplicate detection and review

• references/rich-content.md

  - descriptions, comments, and mentions

• references/administration.md

  - Jira configuration versus workitem data