---
id: "8cd212ea-03e9-47a7-91c4-b956089b5e25"
name: "Jira automation helpers"
micro_summary: "Compact reference for browser-harness helpers that perform Jira create/update/comment/assign operations. Idempotent create, priority mapping, ADF comment formatting, next-gen epic/parent handling, and safe usage examples."
status: "in_progress"
see_also: []
scope: "Compact reference for browser-harness helpers that perform Jira create/update/comment/assign operations. Idempotent create, priority mapping, ADF comment formatting, next-gen epic/parent handling, and safe usage examples."
warnings: "These helpers perform writes — use with caution. Prefer dry-run first (bto_jira_self_check + bto_jira_create with preferred_key to detect existence).\n2026-08-15: runtime verification confirmed all ten bto_jira_* helpers callable from the config-workspace helper surface and the read-only identity check passed."
---
## Purpose
Small durable helpers for browser-harness automation against a Jira Cloud instance. Provides idempotent create, ADF comments, priority token mapping (P0/P1/P2), assign-by-accountId, issuetype changes, and parent/epic handling.

## Helpers (public API)
- bto_jira_create(summary, description, project_key='SFAI', issuetype='Task', preferred_key=None, priority=None, parent=None)
- bto_jira_add_comment(issue_key, text)
- bto_jira_set_priority(issue_key, priority_token_or_name)
- bto_jira_assign(issue_key, account_id)
- bto_jira_set_parent(issue_key, parent_key)
- bto_jira_change_issuetype(issue_key, issuetype_name)
- bto_jira_self_check() — quick /myself check

## Usage notes
- All helpers try to reuse an existing authenticated Jira tab (list_tabs() → switch_tab()).
- Comments use minimal ADF payloads to avoid "Comment body is not valid" errors.
- Priority tokens map by default: P0→Highest, P1→High, P2→Medium; pass explicit Jira priority name to use that value.
- Epic/parent handling: helper sets parent via issue PUT (works for this org's next-gen project). Classic projects may require Agile epic APIs — helper detects failures and surfaces them.

## Safety
- These helpers perform writes — use with caution. Prefer dry-run first (bto_jira_self_check + bto_jira_create with preferred_key to detect existence).