# Manage Jira Cloud Workflows

Teams lose time switching between AI tools and Jira. This skill helps Claude, Codex, and Claude Code search, update, and manage Jira Cloud issues.

## Install

```bash
npx skillstore add joseph obrien/89jobrien-jira
```

## Metadata

- Status: approved
- Slug: 89jobrien-jira
- Version: 1.0.1
- Author version: 1.0.1
- Skillstore revision: r1
- Version status: valid
- Tree hash: 8b5e46c69a8a800955435574c5aebe6e4fc9cbbb6d46b62527b1688e14031c19
- Author: Joseph OBrien
- GitHub username: 89jobrien
- License: MIT
- Repository: https://github.com/89jobrien/steve/tree/main/steve/skills/jira
- Ref: c4037264bbd363c572662d6154a3ab28f5ca4f53
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/89jobrien-jira
- Manifest: https://skillstore.pages.dev/api/skills/89jobrien-jira/manifest

## Capabilities

- Retrieve Jira issue details through Jira Cloud REST API v3.
- Search Jira issues with JQL queries and common query patterns.
- Create and update issues with structured Jira field payloads.
- Add ADF-formatted comments and descriptions to Jira issues.
- Transition issue status and assign or unassign issues.
- Reference Jira endpoints, JQL syntax, and Atlassian Document Format examples.

## Use Cases

- Triage Sprint Work: Find active issues, review owners and status, and identify tickets that need follow-up.
- Create Structured Tickets: Turn requirements into Jira tasks with summaries, labels, priorities, and formatted descriptions.
- Automate Routine Updates: Add comments, assign tickets, and move issues through configured Jira workflow transitions.

## Prompt Templates

### Find My Open Issues

```
Search Jira for my unresolved issues in project PROJECT_KEY and summarize priority, status, and latest update.
```

### Review One Ticket

```
Get Jira issue PROJECT_KEY-123 and summarize the current status, assignee, blockers, and next useful action.
```

### Create a Work Item

```
Create a Jira task in project PROJECT_KEY with this title, acceptance criteria, priority, and labels. Use a valid ADF description.
```

### Plan Bulk Triage

```
Build a JQL query for stale in-progress issues, explain the matching criteria, then propose safe updates for each result.
```

## Limitations

- Requires Jira Cloud network access and valid API credentials.
- Cannot bypass Jira project permissions, workflow rules, or required fields.
- Requires valid ADF structure for rich text descriptions and comments.
- Does not include a graphical Jira client or offline issue cache.

## Best Practices

- Use least-privilege Jira API tokens and rotate them on a regular schedule.
- Preview issue updates before writing comments, assignments, or transitions.
- Keep JQL queries narrow to avoid large responses and rate limits.

## Anti Patterns

- Do not store Jira API tokens in committed files or shared prompts.
- Do not run broad update operations without reviewing the affected issue list.
- Do not use this skill to bypass project permissions or approval workflows.

## Security Audit

- Audited at: 2026-07-05T12:41:09.142\+00:00
- Summary: The skill is a legitimate Jira Cloud helper, and most markdown backtick findings are false positives from examples and inline references. It still handles Jira API credentials, reads .env configuration, and makes authenticated outbound requests. The main security concern is that JIRA\_DOMAIN is not validated before credentials are sent.

## Stats

- Views: 447
- Downloads: 19
- Favorites: 0
- Popularity score: 0