jd — AgentGate for Jira CLI

CLI that enables AI agents (Claude Code and others) to interact with Jira through a safe, approval-gated workflow. All proposed changes are queued for human review before being applied to Jira.

Prerequisites

This CLI requires the AgentGate for Jira Forge app to be installed on your Jira Cloud instance. The app provides the backend API, token management, and the human approval workflow.

Install it from the Atlassian Marketplace.

Install

npm install -g @orbiscend/jd-cli

Quick Start

# 1. Configure endpoint, project, and token
jd init

# 2. Verify connection
jd status

# 3. Read issues
jd issues show PROJ-123
jd issues show PROJ-123 -c     # full context (parent, children, links)
jd issues children PROJ-100

# 4. Propose changes (creates pending changes for human review)
jd changes create --type update --issue PROJ-123 --summary "New title"
jd comment PROJ-123 --body "Analysis complete"

# 5. Review pending changes
jd prime

# 6. Approve or reject
jd changes approve <change-id>
jd changes reject <change-id> --reason "Not needed"

Commands

| Command | Description | |---------|-------------| | jd init | Configure endpoint, project, and token | | jd status | Check connection and token validity | | jd prime | Show pending changes ready for review | | jd comment KEY --body TEXT | Add a comment (pending approval) | | jd issues show KEY | Show issue details | | jd issues show KEY -c | Full context (parent, children, links, comments) | | jd issues children KEY | List child issues | | jd issues list | Search issues (supports --status, --assignee, --type) | | jd issues assign KEY me | Assign issue to yourself | | jd issues transition KEY "Status" | Transition issue status | | jd changes create --type TYPE | Propose a new change | | jd changes list | List pending changes | | jd changes show ID | Show change details | | jd changes update ID | Modify a pending change | | jd changes cancel ID | Cancel a pending change | | jd changes approve ID | Approve a change | | jd changes reject ID | Reject a change | | jd config show | Show current configuration | | jd config set KEY VALUE | Set a configuration value | | jd workflow describe | Show project workflow (issue types and statuses) | | jd autocomplete [SHELL] | Shell completion setup |

Shell Completion

# Zsh
printf "$(jd autocomplete script zsh)" >> ~/.zshrc && source ~/.zshrc

# Bash
printf "$(jd autocomplete script bash)" >> ~/.bashrc && source ~/.bashrc

Once enabled:

jd <TAB>                # Complete commands
jd changes <TAB>        # Complete subcommands
jd issues show --<TAB>  # Complete flags

Global Flags

| Flag | Description | |------|-------------| | --json | Output as JSON (machine-readable) | | --endpoint URL | Override Forge app endpoint | | --project KEY | Jira project key (env: JD_PROJECT) | | --token TOKEN | Override API token |

Exit Codes

| Code | Meaning | |------|---------| | 0 | Success | | 1 | Usage/configuration error | | 2 | API/service error | | 3 | Authentication error | | 4 | Internal/unexpected error |

MCP Server

For MCP integration (Claude Desktop, Claude Code), see @orbiscend/jd-mcp.

Links

• Orbiscend
• AgentGate on Atlassian Marketplace