Jira

Name: Jira
Author: openclaw

BSecurity

Manage Jira issues, boards, sprints, and projects via the jira-cli. Search, create, update, and transition issues directly from the command line.

665 stars
0 votes
0 copies
3 views
Added February 7, 2026

toolsgitapisecurity

Works with

Security analysis

B75/100

criticalModifies startup scripts or system services for persistence

Pro scans all 2 files and shows the line behind each finding

Scanned February 10, 2026

npx -y skills add openclaw/skills --skill jira --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jira?

Add the live security badge to your README. It updates with every re-scan.

[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/openclaw-jira/badge)](https://www.skillsdirectory.com/skills/openclaw-jira)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: jira
description: Manage Jira issues, boards, sprints, and projects via the jira-cli. Search, create, update, and transition issues directly from the command line.
homepage: https://github.com/ankitpokhrel/jira-cli
metadata: {"clawdbot":{"emoji":"🎫","requires":{"bins":["jira"]},"install":[{"id":"brew","kind":"brew","formula":"jira-cli","bins":["jira"],"label":"Install jira-cli (brew)"}]}}
---

# jira

Use `jira` to manage Jira issues, sprints, and boards. Requires API token setup.

## Setup (once)

1. Generate an API token: https://id.atlassian.com/manage-profile/security/api-tokens
2. Export it: `export JIRA_API_TOKEN="your-token"` (add to ~/.zshrc for persistence)
3. Initialize: `jira init --server https://your-org.atlassian.net --login you@email.com --installation cloud`

## Common commands

### Issues
- List issues: `jira issue list -p PROJECT`
- View issue: `jira issue view PROJ-123`
- Create issue: `jira issue create -p PROJECT -t "Task" -s "Summary" -b "Description"`
- Edit issue: `jira issue edit PROJ-123 -s "New summary"`
- Assign issue: `jira issue assign PROJ-123 "user@email.com"`
- Transition issue: `jira issue move PROJ-123 "In Progress"`
- Comment: `jira issue comment add PROJ-123 "My comment"`
- Search (JQL): `jira issue list -q "project = MKT AND status = 'To Do'"`

### Sprints
- List sprints: `jira sprint list -p PROJECT`
- View active sprint: `jira sprint list -p PROJECT --state active`
- Sprint issues: `jira sprint list -p PROJECT --state active --plain`

### Boards
- List boards: `jira board list -p PROJECT`

### Epics
- List epics: `jira epic list -p PROJECT`
- View epic: `jira epic view PROJ-100`

### Projects
- List projects: `jira project list`

## Output formats
- `--plain` — Tab-separated, no colors (best for scripting)
- `--columns key,summary,status` — Select columns
- `--no-truncate` — Don't truncate long fields

## Tips
- Set default project in config: `~/.config/.jira/.config.yml`
- Use JQL for complex queries: `-q "assignee = currentUser() AND status != Done"`
- Open in browser: `jira open PROJ-123`

## Notes
- Confirm with user before creating/editing/transitioning issues
- For bulk operations, show what will change before executing