jira-refresh git:20260820.e07df69A

Immutable. This exact content is served forever at /api/v1/blob/070bdc881468c334.

---
name: jira-refresh
description: Reviewed refresh and confirmed Jira coordination write-back processor for tracker-origin artifacts.
allowed-tools: Read Bash
metadata:
  boundaries:
    - network_fetch
    - filesystem_read_untrusted
    - filesystem_write
  credentialed: true
  primitive-class: credentialed-cli
  auth: sso-cookie
  auth-fallback: creds
  namespace: jira
  keys: ["API_TOKEN"]
---

# Jira Refresh

This processor is invoked by `work-intake` refresh after the shared refresh
runtime has resolved the artifact, lifecycle, authority record, approver, and
confirmation. It does not create artifacts, classify tracker content, or select
processors.

The installed `references/refresh-profile.json` is adopter configuration for
the trusted Jira destination. Set its destination to the same approved host
used by the local Jira client before enabling refresh; tracker data cannot
change it.

Supported write-back is limited to existing Jira client commands:

- `comment` uses `add_comment`.
- `display-status` uses `transition_issue`.
- `closure` uses `transition_issue`.

Trace links, pull-request links, requirement fields, and arbitrary custom field
updates are unsupported unless a future Jira client adds a narrow command for
that action. Jira SSO-cookie authentication remains read-only for refresh:
every non-GET/HEAD write-back action refuses before the client transport is
called.