Jira Integration

Pro v1.0.0

Manage Jira issues, epics, sprints, and projects from the command line

Requires Claude Code CLI

This skill integrates with Jira through Claude Code. Install Claude Code and add this skill to use it.

Available Actions

List Issues

View issues from your board or project with filtering options

Parameters

Name Type Required Description
project string Optional Project key to filter by
status string Optional Filter by status
assignee string Optional Filter by assignee email or 'me'
current-sprint boolean Optional Show only issues in current sprint

Try saying...

  • "Show me all open issues"
  • "List issues in current sprint"
  • "What issues are assigned to me?"
  • "Show all bugs in PROJECT-X"

Create Issue

Create a new issue with title, description, type, and priority

Parameters

Name Type Required Description
type string Required Issue type
summary string Required Issue title/summary
body string Optional Issue description
priority string Optional Issue priority
project string Optional Project key

Try saying...

  • "Create a new bug for the login page"
  • "Add a story for user authentication"
  • "Create a high priority task to fix the API"

View Issue

Get full details of a specific issue including comments and history

Parameters

Name Type Required Description
issue_key string Required Issue key (e.g., TEAM-123)

Try saying...

  • "Show me the details of TEAM-123"
  • "What's the status of issue PROJ-456?"
  • "View TEAM-789"

Transition Issue

Move an issue through workflow states (To Do, In Progress, Done, etc.)

Parameters

Name Type Required Description
issue_key string Required Issue key to transition
transition string Optional Target status/transition name

Try saying...

  • "Move TEAM-123 to In Progress"
  • "Mark TEAM-456 as done"
  • "Transition issue PROJ-789 to Review"

Assign Issue

Assign an issue to a team member or yourself

Parameters

Name Type Required Description
issue_key string Required Issue key to assign
assignee string Required Email address or 'me'

Try saying...

  • "Assign TEAM-123 to me"
  • "Assign this issue to john@company.com"
  • "Make me the assignee for PROJ-456"

Add Comment

Add a comment to an existing issue

Parameters

Name Type Required Description
issue_key string Required Issue key to comment on
message string Required Comment text

Try saying...

  • "Add a comment to TEAM-123 saying it's fixed"
  • "Comment on PROJ-456 with the solution"
  • "Leave a note on TEAM-789"

List Epics

View all epics in a project

Parameters

Name Type Required Description
project string Optional Project key

Try saying...

  • "Show me all epics"
  • "List epics in PROJECT"
  • "What are the active epics?"

List Sprints

View sprints for a board with state filtering

Parameters

Name Type Required Description
state string Optional Sprint state filter

Try saying...

  • "Show me active sprints"
  • "List all sprints"
  • "What sprints are planned?"

Log Work

Track time spent on an issue

Parameters

Name Type Required Description
issue_key string Required Issue key to log work for
time_spent string Required Time duration (e.g., 2h, 30m, 1h 30m)
comment string Optional Work description

Try saying...

  • "Log 2 hours on TEAM-123"
  • "Track 4 hours of work on PROJ-456"
  • "Record time spent on issue TEAM-789"

Getting Started

CLI Authentication Easy Setup
  1. 1 Go to https://id.atlassian.com/manage-profile/security/api-tokens
  2. 2 Click 'Create API token'
  3. 3 Give it a descriptive name and set expiration (1-365 days)
  4. 4 Copy the token (shown only once)
  5. 5 Add to shell config: echo 'export JIRA_API_TOKEN="YOUR_TOKEN"' >> ~/.zshrc
  6. 6 Restart terminal or run: source ~/.zshrc
  7. 7 Run: jira init
  8. 8 Select 'Cloud' and enter your Jira site URL and email

Verify Setup

jira issue list

Success: Displays list of issues or empty list message

View full setup guide

Security & Access

Access Scope

Full access to all Jira projects and issues your account can access. The API token has the same permissions as your user account.

  • API tokens grant full access to your Jira account - treat them like passwords
  • Tokens expire after 1 year by default (1-365 days configurable)
  • Revoke tokens immediately if compromised
  • Never commit tokens to version control
  • Use scoped tokens when possible to limit permissions

Limitations

  • CLI requires Jira Cloud or Data Center instance
  • API tokens expire after 1 year by default
  • Some advanced features may require admin permissions
  • JQL queries have complexity limits

Get This Skill

Requires Pro subscription ($9/month)

Quick Reference

Type
CLI
Auth
CLI Authentication
Setup
Easy Setup
Tools Required
Bash
CLI Dependencies
jira-cli

Documentation

Have Feedback?

Help us improve this skill by sharing your ideas and suggestions.

Request Improvements