kyjus25/clawdbot-jira-skill
Overview
This skill lets you manage Jira Cloud issues, transitions, assignments, comments, and worklogs from the command line. It integrates with the Jira REST API and exposes a small set of scripts to search, create, update status, and report time. Setup requires an Atlassian API token and standard CLI tools like curl, jq, bc, and python3. Use environment variables to scope requests to a project or board.
How this skill works
Scripts call Jira Cloud REST endpoints using your email and API token for basic auth. Operations include fuzzy searches, retrieving issue details, listing and validating transitions before moving issues, assigning users (including self-assign), adding comments, creating tasks, and adding worklogs. Time-reporting commands aggregate worklogs into JSON for a date range, by day, or per issue; some endpoints use worklog/updated and worklog/list which may take a few seconds on large datasets.
When to use it
- Quickly find or open Jira issues from a terminal or script
- Move issues through workflow states while validating allowed transitions
- Assign issues or add comments without opening the web UI
- Create tasks and log work time from shell scripts or CI tools
- Generate JSON summaries of logged hours for integrations or reports
Best practices
- Store JIRA_EMAIL, JIRA_API_TOKEN, and JIRA_URL in environment variables and avoid committing them
- Optionally set JIRA_BOARD to limit searches to a project or leave empty to search globally
- Validate transitions using the transitions command before calling status to avoid failures
- Use the hours JSON output for programmatic consumption rather than parsing human-readable text
- Allow a few seconds for worklog queries on large projects; scripts use worklog/updated + worklog/list
Example use cases
- Search for recent bugs containing a keyword and open the Jira link in a browser
- Move a ticket to In Progress after picking it up and confirm the transition is allowed
- Assign an issue to a teammate by name or to yourself with assign-me
- Log 2.5 hours against an issue for a specific date from a local time-tracking script
- Export logged hours for a week as JSON and feed them into payroll or reporting tools
FAQ
You need your Atlassian account email and an API token; set JIRA_EMAIL and JIRA_API_TOKEN as environment variables.
Can I limit searches to a project?
Yes—set JIRA_BOARD to a project key (comma-separated allowed) to scope searches; leave empty to search all.