kyjus25

Jira

商业运营v1.0.2
作者:kyjus25更新于 2026-05-11共 3 个版本 · 最新版本发布于 2026-01-20clawdbot-jira-skill@clawhub_kyjus25/clawdbot-jira-skill
项目管理用户运营#Jira#Rest Api

据 AlphaMoat 统计,截至 2026-09,Jira 累计下载 4,002 次、获 5 个星标,在全部 5,078 个 AI 技能中排名第 2,557 位,在「商业运营」分类(297 个)中排名第 145 位。

累计安装
127
累计下载
4,002
星标
5
全站排名
#2,557
全站前 51% · 「商业运营」前 49%
平台累计安装累计下载星标评论
ClawHub ↗1273,7745-
SkillHub ↗1254,0025—

各平台的计数口径不同,统计时间不一致。

这个技能是做什么的

该技能通过 Jira Cloud REST API 查询和管理 Jira issue,可执行状态流转并处理工时记录。部分命令会更改 Jira 数据,例如状态、负责人、评论、创建 issue 或更新工时;运行写操作前应核对目标 issue、负责人、评论内容、状态及工时。 需要 JIRA_URL、JIRA_EMAIL 和 JIRA_API_TOKEN;每次写入前取得明确授权。

资料发布于 2026-10-29

可以用来做什么

  • 查询和管理 Jira issue
  • 执行 issue 状态流转
  • 记录或更新工时

什么时候用

  • 需要通过 Jira Cloud API 处理 issue 时
  • 需要更新状态或负责人时
  • 需要记录工时且可以先确认写入内容时

示例提示词

以下是根据技能文档生成的示例,不代表实际运行结果。

查看指定 Jira issue 的当前状态和工时;如需修改,请先给我展示目标 issue、变更内容和将记录的工时,等待确认后再执行。

月度数据趋势

累计下载4,002
2,6253,3654,1042026-03 · 累计下载 2,7272026-05 · 累计下载 3,2242026-06 · 累计下载 3,3432026-07 · 累计下载 3,5922026-08 · 累计下载 3,7422026-09 · 累计下载 4,00226-0326-09
星标5
4562026-03 · 星标 52026-05 · 星标 52026-06 · 星标 52026-07 · 星标 52026-08 · 星标 52026-09 · 星标 526-0326-09

2026-09 起统计方法调整:同名技能按作者分别统计,并覆盖全部技能。图中虚线为调整前的月份,与之后的数据不直接比较,也不计算跨越调整的增长。

月份累计下载环比星标
2026-094,002—5
2026-083,742+4.2%5
2026-073,592+7.4%5
2026-063,343+3.7%5
2026-053,224—5
2026-032,727—5

SKILL.md 原文

以下是作者发布的原始文件,按纯文本显示,本站未做修改或审核;其中的链接不可点击,命令请核实后再运行。抓取于 2026-10-23。

4.2 KB · ClawHub v1.0.2
---
name: jira
description: Manage Jira issues, transitions, and worklogs via the Jira Cloud REST API.
homepage: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/
metadata:
  {
    "clawdbot":
      {
        "emoji": "🧭",
        "requires":
展开全部(共 155 行)
          {
            "bins": ["curl", "jq", "bc", "python3"],
            "env": ["JIRA_URL", "JIRA_EMAIL", "JIRA_API_TOKEN"],
            "optional_env": ["JIRA_BOARD"],
          },
      },
  }
---

# Jira Skill

Work with Jira issues and worklogs from Clawdbot (search, status, create, log work, worklog summaries).

## Setup

1. Get your API key: https://id.atlassian.com/manage-profile/security/api-tokens
2. Click "Create API Token"
3. Set environment variables:
   ```bash
   export JIRA_EMAIL="[email protected]"
   export JIRA_API_TOKEN="your-api-token"
   export JIRA_URL="https://your-domain.atlassian.net"
   # Optional project scope (comma-separated). Empty = search all.
   export JIRA_BOARD="ABC"
   ```

Requires `curl`, `jq`, `bc`, and `python3`.

## Quick Commands

All commands live in `{baseDir}/scripts/jira.sh`.

- `{baseDir}/scripts/jira.sh search "timeout" [max]` — fuzzy search by summary or key inside `JIRA_BOARD`
- `{baseDir}/scripts/jira.sh link ABC-123` — browser link for an issue
- `{baseDir}/scripts/jira.sh issue ABC-123` — quick issue details
- `{baseDir}/scripts/jira.sh status ABC-123 "In Progress"` — move an issue (validates available transitions)
- `{baseDir}/scripts/jira.sh transitions ABC-123` — list allowed transitions
- `{baseDir}/scripts/jira.sh assign ABC-123 "name or email"` — assign by user search
- `{baseDir}/scripts/jira.sh assign-me ABC-123` — assign to yourself
- `{baseDir}/scripts/jira.sh comment ABC-123 "text"` — add a comment
- `{baseDir}/scripts/jira.sh create "Title" ["Description"]` — create a Task in `JIRA_BOARD`
- `{baseDir}/scripts/jira.sh log ABC-123 2.5 [YYYY-MM-DD]` — log hours (defaults to today UTC)
- `{baseDir}/scripts/jira.sh my [max]` — open issues assigned to you
- `{baseDir}/scripts/jira.sh hours 2025-01-01 2025-01-07` — your logged hours by issue (JSON)
- `{baseDir}/scripts/jira.sh hours-day 2025-01-07 [name|email]` — logged hours for a day grouped by user/issue; optional filter (name/email; also resolves to accountId)
- `{baseDir}/scripts/jira.sh hours-issue ABC-123 [name|email]` — logged hours for an issue; optional filter (name/email; also resolves to accountId)

## Command Reference

- **Search issues**

  ```bash
  {baseDir}/scripts/jira.sh search "payment failure" [maxResults]
  ```

- **Issue link**

  ```bash
  {baseDir}/scripts/jira.sh link ABC-321
  ```

- **Issue details**

  ```bash
  {baseDir}/scripts/jira.sh issue ABC-321
  ```

- **Update status**

  ```bash
  {baseDir}/scripts/jira.sh status ABC-321 "Done"
  ```

- **List transitions**

  ```bash
  {baseDir}/scripts/jira.sh transitions ABC-321
  ```

- **Assign issue**

  ```bash
  {baseDir}/scripts/jira.sh assign ABC-321 "Jane Doe"
  ```

- **Assign to yourself**

  ```bash
  {baseDir}/scripts/jira.sh assign-me ABC-321
  ```

- **Add comment**

  ```bash
  {baseDir}/scripts/jira.sh comment ABC-321 "Deployed to staging"
  ```

- **Create issue**

  ```bash
  {baseDir}/scripts/jira.sh create "Fix auth timeout" "Users being logged out after 5m"
  ```

- **Log hours**

  ```bash
  {baseDir}/scripts/jira.sh log PB-321 1.5 2025-01-18
  ```

- **My open issues**

  ```bash
  {baseDir}/scripts/jira.sh my [maxResults]
  ```

- **Logged hours by issue (me)**

  ```bash
  {baseDir}/scripts/jira.sh hours 2025-01-01 2025-01-05
  ```

- **Logged hours for a day (everyone)**

  ```bash
  {baseDir}/scripts/jira.sh hours-day 2025-01-05
  ```

- **Logged hours for a day (user filter)**

  ```bash
  {baseDir}/scripts/jira.sh hours-day 2025-01-05 "jane"
  ```

- **Logged hours for an issue**
  ```bash
  {baseDir}/scripts/jira.sh hours-issue ABC-321 "jane"
  ```

## Notes

- Worklog commands use Jira's worklog/updated + worklog/list combo and may take a few seconds on large projects.
- `hours` filters by `JIRA_EMAIL`; `hours-day` returns all users with totals per issue and user.
- Outputs for hours commands are JSON for reuse in other tools.
- Status transitions are validated against the server-provided transition list before applying.

「商业运营」分类下的热门技能

数据月份:2026-09 · 下载/星标/安装数聚合自公开技能注册库(ClawHub、SkillHub),按月更新。口径说明见数据方法。