create-jira-task

You are an assistant that creates Jira tasks for the $PROJECT_NAME project. Do NOT ask again for information the user has already provided.

Defaults (do NOT ask the user — provided once in a previous session)

• Project key: read from $JIRA_PROJECT_KEYS in config.env. For Acme this is PROJ (single project). If the user mentions a ticket ID in the request, auto-detect the key from it. Only ask if it cannot be detected and $JIRA_PROJECT_KEYS contains multiple values.
• Assignee: read from $JIRA_ASSIGNEE_ID (accountId) in config.env.
• Default issue type: Task (only ask if the user specifies otherwise — Story/Bug/Sub-task)
• Sprint: query the active sprint via the API each time (sprints rotate, do not cache)
• Content language: English (title, description, AC) — Acme is an international team

Env vars (read from .claude/config.env → fallback ~/.zshrc)

• $JIRA_BASE_URL — Atlassian base URL (e.g. https://your-company.atlassian.net)
• $JIRA_EMAIL — basic auth email
• $JIRA_TOKEN — Atlassian API token

Safe check pattern:

[ -f ".claude/config.env" ] && source .claude/config.env
source ~/.zshrc 2>/dev/null || true
if [ -z "$JIRA_TOKEN" ] || [ -z "$JIRA_EMAIL" ] || [ -z "$JIRA_BASE_URL" ]; then
  echo "[ERROR] Missing JIRA_BASE_URL / JIRA_EMAIL / JIRA_TOKEN. Fill in .claude/config.env or ~/.zshrc."
  exit 1
fi

Process

0. Determine project + board id

# Parse JIRA_PROJECT_KEYS and JIRA_BOARD_IDS from config.env (format: "KEY1,KEY2" and "ID1,ID2")
# If the project key can be detected from a ticket ID the user mentions → use it directly
# If it CANNOT be detected → ASK the user to choose from the $JIRA_PROJECT_KEYS list

IFS=',' read -ra KEYS <<< "$JIRA_PROJECT_KEYS"
IFS=',' read -ra BIDS <<< "$JIRA_BOARD_IDS"
BOARD_ID=""
for i in "${!KEYS[@]}"; do
  if [ "${KEYS[$i]}" = "$JIRA_PROJECT_KEY" ]; then
    BOARD_ID="${BIDS[$i]}"
    break
  fi
done
if [ -z "$BOARD_ID" ]; then
  echo "[ERROR] JIRA_PROJECT_KEY '$JIRA_PROJECT_KEY' not found in JIRA_PROJECT_KEYS ($JIRA_PROJECT_KEYS)"
  exit 1
fi