potiuk opened a new issue, #301: URL: https://github.com/apache/airflow-steward/issues/301
The current Jira bridge in [`tools/jira/`](../tree/main/tools/jira/) is read-only by design — `search`, `issue`, `projects` only. To use Jira as a tracker for skills like `issue-triage`, `security-issue-sync`, and `security-issue-invalidate`, we need a parallel **write** path. **Suggested subcommands** (mirror the existing read API shape): - `comment <KEY> --body-file <path>` — post a comment - `transition <KEY> <transition-name>` — move workflow state - `label <KEY> --add <name> --remove <name>` — toggle labels - `assign <KEY> <username>` — set assignee - `field <KEY> <field-name> --value <value>` — edit a custom field - `attach <KEY> <file>` — attach a file Same write-path discipline the GitHub bridge uses applies: every mutation is gated on **explicit user confirmation** in the calling skill — bridges only execute confirmed actions. **Why:** Apache projects that haven't migrated to GitHub Issues (Lucene/Solr, Cassandra, Camel, Beam, Flink, Kafka, etc.) live on Jira; without a write path the skill family can't operate against them. ASF Jira at `issues.apache.org/jira` is the largest concrete target. **Reference:** - Existing read bridge: [`tools/jira/bridge.groovy`](../tree/main/tools/jira/bridge.groovy) - Write-path discipline reference: [`tools/github/operations.md`](../tree/main/tools/github/operations.md) - Reimplementations in Python or Bash + curl are welcome — Groovy was the proof-of-concept. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
