Jira

Create the MOB ticket

Project MOB, board 5348. Auth = JIRA_EMAIL + JIRA_API_TOKEN (Perforce Atlassian). Ids below are the known MOB values — treat them as config the caller may override.

• Type: Task (10013)
• Product = Blazemeter — customfield_10350 (id 21409)
• Scrum Team = Terra — customfield_10067 (id 21406)
• Sprint = active sprint of board 5348 — customfield_10020
• Assignee = the repo owner — resolve the display name → accountId via /rest/api/3/user/search?query=<owner>; if owner is empty, fall back to tcohen. (Assignee is how ownership is tracked — there's no GitHub reviewer.)
• Status → In Review — transition id 61.
• Labels — set fields.labels to whatever the caller passes (Jira labels allow no spaces; use _). The mend-blz caller passes mend_orch so every orchestrator-created ticket is filterable (JQL labels = mend_orch); include any others the caller supplies alongside it.

Summary & description

• Summary: supplied by the calling skill — this skill only knows Jira mechanics, not what to call the ticket. E.g. the mend-blz skill passes Fix Mend vulnerabilities <repository name> (the repo's short name, e.g. Fix Mend vulnerabilities a.blazemeter.com — not the component alias).
• Description at creation time (the ticket is created before the PR exists — see "Updating after the PR exists" below — so there is no PR link yet), in this order:
  1. Dependencies fixed — one line each library: <from> → <to> + severity/CVE.
  2. Jenkins build link.
  3. Confluence tracking-page link — only when the caller reports deferred/unfixed items (e.g. mend-blz's Confluence report step); omit this line entirely when there's nothing deferred or the caller skipped that report. The page must already reflect the current run before this ticket is created — create the ticket after the caller's Confluence write, not before.

A nojira flag skips ticket create/update entirely.

Updating after the PR exists

Once the caller opens the PR (which carries this ticket's id in its title from creation — see the github skill), it calls back into this skill to add the PR link to the ticket description: read the current description and insert the PR link as its own line directly after "Dependencies fixed" and before the Jenkins build link — i.e. the final description reads dependencies → PR link → Jenkins link → Confluence link (if any), even though PR and Jenkins were written in the opposite order. Jira's API requires the full description field on update, so re-send the whole text with the line inserted — don't assume a partial-append endpoint. Skip this step entirely under nojira (there is no ticket) or if the PR never got opened (e.g. the flow stopped before that step).

Rate limits

Jira Cloud returns 429 under load. Back off and retry with a bounded policy, don't loop open-ended: wait ~10s, retry; if 429 again, wait ~30s, retry; if 429 again, wait ~60s, retry once more; still failing after that (3 retries total) → stop and report the failure via the caller's notes/summary mechanism rather than continuing to wait.