File a ticket

The ticket skill (bglad-ticket-mr, help menu MR) or Remy (the delivery agent) with intent create-issue.

Words and menu codes if MR is new.

Task vs Bug

• Task — features, chores, defects on unreleased work.
• Bug — defect on a released version. After create, offer clone onto supported releases.

Squad fields

After the squad picker, do not guess component, development team, or hosts. Prefer Jira MCP.

If jira_component or jira_development_team is still empty on first create, list allowed options from Jira (createmeta, or JQL when createmeta is empty), ASK the user to pick, and save into the squad table in _bmad/custom/bglad-ticket-mr.toml before the create call (see ticket-mr Save a correction / save_team_field.py). Never invent option ids.

Setup may have filled those fields when a Jira client was available; it does not require them at install time.

Print {workflow.jira_host}/browse/{KEY}.

Waiting label

When Dev or Analysis leaves Open questions on a Jira spec and the overlay sets jira_waiting_label, that label is added (and removed when Open questions becomes None). Optional jira_waiting_status transitions the issue when set.

Descriptions: no bold/italics; do not backslash-escape backticks. When spec_store is jira, add Problem / Acceptance / Design / Test notes to the issue — see bglad-ticket-mr references/ticket-spec.md. When the spec lives on Confluence or markdown, still file the Jira Task for tracking if that is how the squad works; do not copy the spec into a second place.