atlassian-jira-by-altf1be
Atlassian Jira Cloud CRUD skill — manage issues, comments, attachments, workflow transitions, and JQL search via Jira REST API v3 with email + API token auth.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install openclaw-skills-atlassian-jira-by-altf1be
Repository
Skill path: skills/abdelkrim/atlassian-jira-by-altf1be
Atlassian Jira Cloud CRUD skill — manage issues, comments, attachments, workflow transitions, and JQL search via Jira REST API v3 with email + API token auth.
Open repositoryBest for
Primary workflow: Run DevOps.
Technical facets: Full Stack, Backend, Security.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: openclaw.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install atlassian-jira-by-altf1be into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/openclaw/skills before adding atlassian-jira-by-altf1be to shared team environments
- Use atlassian-jira-by-altf1be for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: atlassian-jira-by-altf1be
description: "Atlassian Jira Cloud CRUD skill — manage issues, comments, attachments, workflow transitions, and JQL search via Jira REST API v3 with email + API token auth."
homepage: https://github.com/ALT-F1-OpenClaw/openclaw-skill-atlassian-jira
metadata:
{"openclaw": {"emoji": "🎫", "requires": {"env": ["JIRA_HOST", "JIRA_EMAIL", "JIRA_API_TOKEN"]}, "primaryEnv": "JIRA_HOST"}}
---
# Jira Cloud by @altf1be
Manage Atlassian Jira Cloud issues, comments, attachments, and workflow transitions via the REST API.
## Setup
1. Get an API token from https://id.atlassian.com/manage-profile/security/api-tokens
2. Set environment variables (or create `.env` in `{baseDir}`):
```
JIRA_HOST=yourcompany.atlassian.net
[email protected]
JIRA_API_TOKEN=your-api-token
JIRA_DEFAULT_PROJECT=PROJ
```
3. Install dependencies: `cd {baseDir} && npm install`
## Commands
### Issues
```bash
# List issues (optionally filter by project, status, assignee)
node {baseDir}/scripts/jira.mjs list --project PROJ --status "In Progress" --assignee "currentUser()"
# Create an issue
node {baseDir}/scripts/jira.mjs create --project PROJ --type Task --summary "Fix login bug" --description "Users can't log in" --priority High
# Read issue details
node {baseDir}/scripts/jira.mjs read --key PROJ-123
# Update issue fields
node {baseDir}/scripts/jira.mjs update --key PROJ-123 --summary "New title" --priority Low
# Delete issue (requires --confirm)
node {baseDir}/scripts/jira.mjs delete --key PROJ-123 --confirm
# Search with JQL
node {baseDir}/scripts/jira.mjs search --jql "project = PROJ AND status = Open ORDER BY created DESC"
```
### Comments
```bash
# List comments on an issue
node {baseDir}/scripts/jira.mjs comment-list --key PROJ-123
# Add a comment
node {baseDir}/scripts/jira.mjs comment-add --key PROJ-123 --body "This is ready for review"
# Update a comment
node {baseDir}/scripts/jira.mjs comment-update --key PROJ-123 --comment-id 10001 --body "Updated comment"
# Delete a comment (requires --confirm)
node {baseDir}/scripts/jira.mjs comment-delete --key PROJ-123 --comment-id 10001 --confirm
```
### Attachments
```bash
# List attachments on an issue
node {baseDir}/scripts/jira.mjs attachment-list --key PROJ-123
# Upload an attachment
node {baseDir}/scripts/jira.mjs attachment-add --key PROJ-123 --file ./screenshot.png
# Delete an attachment (requires --confirm)
node {baseDir}/scripts/jira.mjs attachment-delete --attachment-id 10001 --confirm
```
### Workflow Transitions
```bash
# List available transitions for an issue
node {baseDir}/scripts/jira.mjs transitions --key PROJ-123
# Move issue to a new status (by transition ID or name)
node {baseDir}/scripts/jira.mjs transition --key PROJ-123 --transition-id 31
node {baseDir}/scripts/jira.mjs transition --key PROJ-123 --transition-name "Done"
```
## Dependencies
- `commander` — CLI framework
- `dotenv` — environment variable loading
- Node.js built-in `fetch` (requires Node >= 18)
## Security
- Email + API token auth (Basic auth via base64 encoding)
- No secrets or tokens printed to stdout
- All delete operations require explicit `--confirm` flag
- Path traversal prevention for file uploads
- Built-in rate limiting with exponential backoff retry
- Lazy config validation (only checked when a command runs)
## Author
Abdelkrim BOUJRAF — [ALT-F1 SRL](https://www.alt-f1.be), Brussels 🇧🇪
X: [@altf1be](https://x.com/altf1be)
---
## Skill Companion Files
> Additional files collected from the skill directory layout.
### README.md
```markdown
# openclaw-skill-atlassian-jira
[](https://opensource.org/licenses/MIT)
[](https://nodejs.org/)
[](https://www.atlassian.com/software/jira)
[](https://clawhub.ai)
[](https://clawhub.ai/skills/atlassian-jira-by-altf1be)
[](https://github.com/ALT-F1-OpenClaw/openclaw-skill-atlassian-jira/commits/main)
[](https://github.com/ALT-F1-OpenClaw/openclaw-skill-atlassian-jira/issues)
[](https://github.com/ALT-F1-OpenClaw/openclaw-skill-atlassian-jira/stargazers)
OpenClaw skill for Atlassian Jira Cloud — CRUD issues, comments, attachments, workflow transitions, and JQL search via Jira REST API v3.
By [Abdelkrim BOUJRAF](https://www.alt-f1.be) / ALT-F1 SRL, Brussels 🇧🇪 🇲🇦
## Table of Contents
- [Features](#features)
- [Quick Start](#quick-start)
- [Setup](#setup)
- [Commands](#commands)
- [Security](#security)
- [ClawHub](#clawhub)
- [License](#license)
- [Author](#author)
- [Contributing](#contributing)
## Features
- **Issues** — Create, read, update, delete, list, and search (JQL)
- **Comments** — Add, update, delete, and list
- **Attachments** — Upload, list, and delete
- **Workflow Transitions** — List available transitions and move issues through workflow states
- **Security** — `--confirm` required for deletes, no secrets to stdout, rate-limit retry with backoff
- **Auth** — Email + API token (Basic auth)
## Quick Start
```bash
# 1. Clone
git clone https://github.com/ALT-F1-OpenClaw/openclaw-skill-atlassian-jira.git
cd openclaw-skill-atlassian-jira
# 2. Install
npm install
# 3. Configure
cp .env.example .env
# Edit .env with your Jira Cloud credentials
# 4. Use
node scripts/jira.mjs list --project PROJ
node scripts/jira.mjs create --project PROJ --summary "My first issue"
node scripts/jira.mjs read --key PROJ-1
```
## Setup
1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
2. Create an API token
3. Copy `.env.example` to `.env` and fill in:
- `JIRA_HOST` — your Jira Cloud instance (e.g. `yourcompany.atlassian.net`)
- `JIRA_EMAIL` — your Atlassian account email
- `JIRA_API_TOKEN` — the API token you just created
- `JIRA_DEFAULT_PROJECT` — (optional) default project key
## Commands
See [SKILL.md](./SKILL.md) for full command reference.
## Security
- Email + API token auth (Basic auth via base64 encoding)
- No secrets or tokens printed to stdout
- All delete operations require explicit `--confirm` flag
- Built-in rate limiting with exponential backoff retry
- Lazy config validation (only checked when a command runs)
## ClawHub
Published as: `atlassian-jira-by-altf1be`
```bash
clawhub install atlassian-jira-by-altf1be
```
## License
MIT — see [LICENSE](./LICENSE)
## Author
Abdelkrim BOUJRAF — [ALT-F1 SRL](https://www.alt-f1.be), Brussels 🇧🇪 🇲🇦
- GitHub: [@abdelkrim](https://github.com/abdelkrim)
- X: [@altf1be](https://x.com/altf1be)
## Contributing
Contributions welcome! Please open an issue or PR.
```
### _meta.json
```json
{
"owner": "abdelkrim",
"slug": "atlassian-jira-by-altf1be",
"displayName": "Atlassian Jira by altf1be",
"latest": {
"version": "1.0.0",
"publishedAt": 1773103849636,
"commit": "https://github.com/openclaw/skills/commit/f19ec4ad42ed500913dab4b40fbdb4f6c12a15c0"
},
"history": []
}
```