管理自托管/企业 Jira 实例的 Jira 问题，使用个人访问令牌（PAT），适用于 SSO/SAML 环境下的 Basic Auth 失效场景。
何时使用此技能
- 自托管 Jira 实例（如 Red Hat、企业部署）
- 启用 SSO/SAML 认证的 Jira 实例
- Basic Auth 和
jira-cli 失效的环境
注意： 对于 Atlassian Cloud 使用电子邮件 + API 令牌认证，请使用 clawdbot-jira-skill。
前提条件
- 转到 Jira 个人资料 → 个人访问令牌
- 创建一个具有适当权限的新令牌
- 将其存储在环境变量
JIRA_PAT 中
- Jira 基础 URL：您的 Jira 实例 URL 在
JIRA_URL 中
工具
该技能使用
curl 和
jq 进行所有操作。
指令
获取问题详细信息
...（保持原文，仅示例）
Manage Jira issues on self-hosted/enterprise Jira instances using Personal Access Tokens (PAT). This skill is designed for environments where Basic Auth doesn't work due to SSO/SAML authentication.
When to Use This Skill
Use this skill when working with:
- Self-hosted Jira instances (e.g., Red Hat, enterprise deployments)
- Jira instances with SSO/SAML authentication
- Environments where
jira-cli or Basic Auth fails
Note: For Atlassian Cloud with email + API token auth, use the clawdbot-jira-skill instead.
Prerequisites
- Personal Access Token (PAT): Create one in Jira:
- Go to your Jira profile → Personal Access Tokens
- Create a new token with appropriate permissions
- Store it in environment variable
JIRA_PAT- Jira Base URL: Your Jira instance URL in
JIRA_URL
Environment Variables
export JIRA_PAT="your-personal-access-token"
export JIRA_URL="https://issues.example.com"
Tools
This skill uses curl and jq for all operations.
Instructions
Get Issue Details
Fetch full details of a Jira issue:
curl -s -H "Authorization: Bearer $JIRA_PAT" \
"$JIRA_URL/rest/api/2/issue/PROJECT-123" | jq
Get specific fields only:
curl -s -H "Authorization: Bearer $JIRA_PAT" \
"$JIRA_URL/rest/api/2/issue/PROJECT-123?fields=summary,status,description" | jq
Search Issues (JQL)
# Find child issues of an epic
curl -s -H "Authorization: Bearer $JIRA_PAT" \
"$JIRA_URL/rest/api/2/search?jql=parent=EPIC-123" | jq# Complex queries (URL-encoded)
curl -s -H "Authorization: Bearer $JIRA_PAT" \
"$JIRA_URL/rest/api/2/search?jql=project%3DPROJ%20AND%20status%3DOpen" | jq
Common JQL patterns:
parent=EPIC-123 - Child issues of an epicproject=PROJ AND status=Open - Open issues in projectassignee=currentUser() - Your assigned issueslabels=security - Issues with specific labelupdated >= -7d - Recently updated
Get Available Transitions
Before changing status, query available transitions:
curl -s -H "Authorization: Bearer $JIRA_PAT" \
"$JIRA_URL/rest/api/2/issue/PROJECT-123/transitions" | jq '.transitions[] | {id, name}'
Transition (Change Status)
Close an issue with a comment:
curl -s -X POST \
-H "Authorization: Bearer $JIRA_PAT" \
-H "Content-Type: application/json" \
-d '{
"transition": {"id": "61"},
"update": {
"comment": [{"add": {"body": "Closed via API"}}]
}
}' \
"$JIRA_URL/rest/api/2/issue/PROJECT-123/transitions"
Add a Comment
curl -s -X POST \
-H "Authorization: Bearer $JIRA_PAT" \
-H "Content-Type: application/json" \
-d '{"body": "Comment added via API."}' \
"$JIRA_URL/rest/api/2/issue/PROJECT-123/comment"
Update Issue Fields
curl -s -X PUT \
-H "Authorization: Bearer $JIRA_PAT" \
-H "Content-Type: application/json" \
-d '{
"fields": {
"summary": "Updated summary",
"labels": ["api", "automated"]
}
}' \
"$JIRA_URL/rest/api/2/issue/PROJECT-123"
Create an Issue
curl -s -X POST \
-H "Authorization: Bearer $JIRA_PAT" \
-H "Content-Type: application/json" \
-d '{
"fields": {
"project": {"key": "PROJ"},
"summary": "New issue via API",
"description": "Issue description",
"issuetype": {"name": "Task"},
"parent": {"key": "EPIC-123"}
}
}' \
"$JIRA_URL/rest/api/2/issue"
Useful jq Filters
# Summary and status
jq '{key: .key, summary: .fields.summary, status: .fields.status.name}'# List search results
jq '.issues[] | {key: .key, summary: .fields.summary, status: .fields.status.name}'
# Issue links
jq '.fields.issuelinks[] | {type: .type.name, key: (.inwardIssue // .outwardIssue).key}'
Troubleshooting
| Error | Cause | Solution |
|---|
| 401 Unauthorized | Invalid/expired PAT | Regenerate token, check Bearer format |
| 404 Not Found | Issue doesn't exist or no access | Verify issue key and permissions |
| 400 Bad Request on transition | Invalid transition ID | Query available transitions first |
Comparison with Basic Auth Skills
This skill uses Bearer token authentication (Authorization: Bearer ), which works with self-hosted Jira instances using SSO/SAML. For Atlassian Cloud with email + API token, use skills that implement Basic Auth instead.
by