jira-communication

Category: Tools & Productivity | Uploader: netresearch | Downloads: 0 | Version: v1.0（Latest）

Use when interacting with Jira issues - searching, creating, updating, transitioning, commenting, logging work, downloading attachments, managing sprints, boards, issue links, fields, or users. Auto-triggers on Jira URLs and issue keys (PROJ-123).

Changelog: Source: GitHub https://github.com/netresearch/jira-skill

Directory Structure

Current level: skills/jira-communication/

📁 references/
- 📄 jql-quick-reference.md 4.6 KB
- 📄 troubleshooting.md 3.5 KB
📁 scripts/
- 📁 core/
  - 📄 jira-attachment.py 9.8 KB
  - 📄 jira-issue.py 13.1 KB
  - 📄 jira-search.py 6.0 KB
  - 📄 jira-setup.py 18.9 KB
  - 📄 jira-validate.py 13.9 KB
  - 📄 jira-worklog.py 7.9 KB
- 📁 lib/
  - 📄 __init__.py 663 B
  - 📄 client.py 10.9 KB
  - 📄 config.py 11.4 KB
  - 📄 output.py 4.5 KB
- 📁 utility/
  - 📄 jira-fields.py 5.8 KB
  - 📄 jira-link.py 4.8 KB
  - 📄 jira-user.py 6.2 KB
- 📁 workflow/
  - 📄 jira-board.py 6.2 KB
  - 📄 jira-comment.py 7.1 KB
  - 📄 jira-create.py 7.5 KB
  - 📄 jira-sprint.py 7.7 KB
  - 📄 jira-transition.py 8.1 KB
📄 AGENTS.md 2.0 KB
📄 SKILL.md 3.8 KB

SKILL.md

---
name: jira-communication
description: "Use when interacting with Jira issues - searching, creating, updating, transitioning, commenting, logging work, downloading attachments, managing sprints, boards, issue links, fields, or users. Auto-triggers on Jira URLs and issue keys (PROJ-123)."
---

# Jira Communication

CLI scripts for Jira operations using `uv run`. All scripts support `--help`, `--json`, `--quiet`, `--debug`.

**Paths** are relative to `skills/jira-communication/`. Run from there or prefix accordingly.

## Auto-Trigger

Trigger when user mentions:
- **Jira URLs**: `https://jira.*/browse/*`, `https://*.atlassian.net/browse/*`
- **Issue keys**: `PROJ-123`, `NRS-4167`

When triggered by URL → extract issue key → run `jira-issue.py get PROJ-123`

## Auth Failure Handling

When auth fails, offer: `uv run scripts/core/jira-setup.py` (interactive credential setup)

## Scripts

| Script | Purpose |
|--------|---------|
| `scripts/core/jira-setup.py` | Interactive credential config |
| `scripts/core/jira-validate.py` | Verify connection |
| `scripts/core/jira-issue.py` | Get/update issue details |
| `scripts/core/jira-search.py` | Search with JQL |
| `scripts/core/jira-worklog.py` | Time tracking |
| `scripts/core/jira-attachment.py` | Download attachments |
| `scripts/workflow/jira-create.py` | Create issues |
| `scripts/workflow/jira-transition.py` | Change status |
| `scripts/workflow/jira-comment.py` | Add/edit/list comments |
| `scripts/workflow/jira-sprint.py` | List sprints |
| `scripts/workflow/jira-board.py` | List boards |
| `scripts/utility/jira-user.py` | User info |
| `scripts/utility/jira-fields.py` | Search fields |
| `scripts/utility/jira-link.py` | Issue links |

## Critical: Flag Ordering

Global flags **MUST** come **before** subcommand:
```bash
# Correct:  uv run scripts/core/jira-issue.py --json get PROJ-123
# Wrong:    uv run scripts/core/jira-issue.py get PROJ-123 --json
```

## Quick Examples

```bash
uv run scripts/core/jira-validate.py --verbose
uv run scripts/core/jira-search.py query "assignee = currentUser()"
uv run scripts/core/jira-issue.py get PROJ-123
uv run scripts/core/jira-worklog.py add PROJ-123 2h --comment "Work done"
uv run scripts/workflow/jira-transition.py do PROJ-123 "In Progress" --dry-run
uv run scripts/workflow/jira-comment.py edit PROJ-123 12345 "Updated comment text"
```

## Related Skills

**jira-syntax**: For descriptions/comments. Jira uses wiki markup, NOT Markdown.

## References

- `references/jql-quick-reference.md` - JQL syntax
- `references/troubleshooting.md` - Setup and auth issues

## Authentication

**Cloud**: `JIRA_URL` + `JIRA_USERNAME` + `JIRA_API_TOKEN`
**Server/DC**: `JIRA_URL` + `JIRA_PERSONAL_TOKEN`

Config via `~/.env.jira` or env vars. Run `jira-validate.py --verbose` to verify.

## Multi-Profile Support

When `~/.jira/profiles.json` exists, multiple Jira instances are supported.

**Profile resolution** (automatic, priority order):
1. `--env-file PATH` → legacy single-file behavior
2. `--profile NAME` flag → use named profile directly
3. Full Jira URL in input → match host to profile
4. Issue key (e.g., WEB-1381) → match project prefix to profile
5. `.jira-profile` file in working directory → use named profile
6. Default profile from profiles.json
7. Fallback to `~/.env.jira`

**When triggered by URL** → host matched to profile automatically.
**When triggered by issue key** → project prefix matched to profile.
**If ambiguous** → ask user which profile to use.

**Profile management**:
```bash
uv run scripts/core/jira-setup.py --profile mkk                    # Create profile
uv run scripts/core/jira-validate.py --profile mkk --verbose        # Validate profile
uv run scripts/core/jira-validate.py --all-profiles                 # Validate all
uv run scripts/core/jira-setup.py --migrate                         # Migrate .env.jira
```

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

jira-communication

Directory Structure

SKILL.md

Report

Notice