Skip to content

aiskillstore/marketplace / skills/89jobrien/jira

Jira Cloud integration for issue management and search. This skill should be used when working with Jira tickets, searching issues with JQL, creating or updating issues, adding comments, or transitioning issue status. Covers REST API v3 and Jira Query Language.

FileKindSize
SKILL.mdskill md4.5 KB
references/adf-format.mdmarkdown4.4 KB
references/api-endpoints.mdmarkdown3.2 KB
references/jql-reference.mdmarkdown4.6 KB
scripts/jira-api.pyexecutablescript4.5 KB
skill-report.jsonconfig70.1 KB

references/api-endpoints.md

View on GitHub
---
author: Joseph OBrien
status: unpublished
updated: '2025-12-23'
version: 1.0.1
tag: skill
type: reference
parent: jira
---

# Jira REST API v3 Endpoints Reference

Base URL: `https://{domain}.atlassian.net/rest/api/3`

## Authentication

All requests require Basic Auth with email and API token:

```bash
AUTH=$(echo -n "email@example.com:API_TOKEN" | base64)
curl -H "Authorization: Basic $AUTH" -H "Content-Type: application/json" ...
```

## Issue Operations

### Get Issue

```
GET /issue/{issueIdOrKey}
```

Query params: `fields`, `expand` (changelog, transitions, renderedFields)

### Create Issue

```
POST /issue
```

```json
{
  "fields": {
    "project": { "key": "PROJ" },
    "issuetype": { "name": "Task" },
    "summary": "Issue title",
    "description": {
      "type": "doc",
      "version": 1,
      "content": [
        {
          "type": "paragraph",
          "content": [{ "type": "text", "text": "Description text" }]
        }
      ]
    },
    "assignee": { "accountId": "user-account-id" },
    "labels": ["label1", "label2"],
    "priority": { "name": "High" }
  }
}
```

### Update Issue

```
PUT /issue/{issueIdOrKey}
```

Same body format as create, only include fields to update.

### Delete Issue

```
DELETE /issue/{issueIdOrKey}
```

### Add Comment

```
POST /issue/{issueIdOrKey}/comment
```

```json
{
  "body": {
    "type": "doc",
    "version": 1,
    "content": [
      {
        "type": "paragraph",
        "content": [{ "type": "text", "text": "Comment text" }]
      }
    ]
  }
}
```

### Get Transitions

```
GET /issue/{issueIdOrKey}/transitions
```

Returns available status transitions for the issue.

### Transition Issue

```
POST /issue/{issueIdOrKey}/transitions
```

```json
{
  "transition": { "id": "21" }
}
```

### Assign Issue

```
PUT /issue/{issueIdOrKey}/assignee
```

```json
{ "accountId": "user-account-id" }
```

To unassign: `{ "accountId": null }`

### Add Labels

```
PUT /issue/{issueIdOrKey}
```

```json
{
  "update": {
    "labels": [
      { "add": "new-label" }
    ]
  }
}
```

### Link Issues

```
POST /issueLink
```

```json
{
  "type": { "name": "Blocks" },
  "inwardIssue": { "key": "PROJ-123" },
  "outwardIssue": { "key": "PROJ-456" }
}
```

## Search

### Search with JQL

```
GET /search?jql={jql}&maxResults=50&startAt=0
```

Or POST for complex queries:

```
POST /search
```

```json
{
  "jql": "project = PROJ AND status = 'In Progress'",
  "startAt": 0,
  "maxResults": 50,
  "fields": ["summary", "status", "assignee"]
}
```

## Project Operations

### List Projects

```
GET /project
```

### Get Project

```
GET /project/{projectIdOrKey}
```

Query params: `expand` (issueTypes, lead, description)

### Get Project Issue Types

```
GET /project/{projectIdOrKey}/statuses
```

## User Operations

### Get Current User

```
GET /myself
```

### Search Users

```
GET /user/search?query={query}
```

### Get User by Account ID

```
GET /user?accountId={accountId}
```

## Common Response Codes

| Code | Meaning |
|------|---------|
| 200 | Success |
| 201 | Created |
| 204 | No content (success) |
| 400 | Bad request - check parameters |
| 401 | Unauthorized - check credentials |
| 403 | Forbidden - check permissions |
| 404 | Not found |
| 429 | Rate limited |
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall