Aleksey Shakhmatov
0725b6b034
- descriptions state WHEN each skill applies - jira-workflow ships curl scripts reading TRACKER_URL/JIRA_TOKEN from env, no hardcoded secrets/URLs - repo-map/docs-map defer values to session corporate context; company specifics left as TODO - go-standards uses realistic Go defaults, company-specific bits marked TODO
18 lines
732 B
Bash
Executable File
18 lines
732 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# get-issue.sh <ISSUE_KEY>
|
|
# Prints summary, status and description of a tracker issue.
|
|
# Reads TRACKER_URL and JIRA_TOKEN from the environment. No secrets are hardcoded.
|
|
set -euo pipefail
|
|
|
|
KEY="${1:?usage: get-issue.sh <ISSUE_KEY>}"
|
|
: "${TRACKER_URL:?set TRACKER_URL (or take the tracker address from the session corporate context)}"
|
|
: "${JIRA_TOKEN:?set JIRA_TOKEN (tracker personal access token)}"
|
|
|
|
BASE="${TRACKER_URL%/}"
|
|
|
|
curl -fsS \
|
|
-H "Authorization: Bearer ${JIRA_TOKEN}" \
|
|
-H "Accept: application/json" \
|
|
"${BASE}/rest/api/2/issue/${KEY}?fields=summary,status,description" \
|
|
| { jq -r '"\(.key)\t\(.fields.status.name)\n\(.fields.summary)\n\n\(.fields.description // "")"' 2>/dev/null || cat; }
|