SkillFoxx

Jira CLI

Jira CLI displays issues and sprints as tables or script data, keeping work-item queries in the terminal beside source code.

  • 6,069 ★ on the repository
  • Last commit
  • MIT
CLI

Extended access

Why this level

  • The CLI reads and changes issues with your Jira account rights, including comments and deletion when permitted.
All reasons and checks

ankitpokhrel/jira-cliAuthor:ankitpokhrel

Install

Manual install

docker run -it --rm ghcr.io/ankitpokhrel/jira-cli:latest

First executable README trial via Docker. Authentication is configured separately.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The CLI reads and changes issues with your Jira account rights, including comments and deletion when permitted.

This is third-party code. Review the repository files before installing.

What it does

Jira CLI brings Jira issue workflows to the terminal. Users filter and inspect issues, returning an interactive table or script-friendly output. Commands also create and edit issues, assign people and transition statuses. Users can list issues in the current sprint or a selected epic. An agent with terminal access can prepare a selection and proposed edits before applying them.

Who it is for. Engineering leads reviewing Jira issues and sprints from the terminal beside their repositories.

Good fit when

  • Before standup, you inspect assigned issues with a selected status and label.
  • A lead exports an issue list as CSV or JSON for a report.
  • The team prepares a recurring field-update script and reviews it before execution.
  • You maintain several Jira projects and select a separate configuration for each.

Not a fit when

  • The account lacks project access or issue permissions.
  • You need a complete visual replacement for every Jira page and extension.
  • A script would update issues without checking project and workflow states.

Example request

Export my open issues from the current sprint as JSON and suggest clarifications. Make no Jira changes.

Limitations

Jira Cloud or on-premises credentials are required, with authentication selected during initialization. Localized Jira Server instances may need issue-type names entered manually in configuration. Some Atlassian formatting nodes are not translated accurately, so review descriptions after writes. Commands inherit account permissions rather than a separate agent role; grant only the rights needed for the automation.

How to disable. Uninstall the CLI or container and revoke its Jira token. Configuration files and previously changed issues remain separately.

FAQ

How do I configure a connection?

Run `jira init` and select Cloud or Local. Supply the token separately without exposing it in chat.

How do I get JSON?

Use `jira issue list --raw`; `--csv` provides CSV.

How do I disable the interactive table?

Add `--plain` for output consumed by another command.

Can issues be created non-interactively?

Yes. Pass the fields as parameters and add `--no-input`. Before running, show the proposed values to the person responsible for the issues.

How do I switch projects?

Select a config with `--config` or `JIRA_CONFIG_FILE` and verify the project before writes.

Discussion

No questions or reviews yet.

CLI tools

A plugin that works Jira from the agent terminal: JQL search, issues, sprints, worklogs and wiki markup validation

PluginBroad access90

Jira MCP in Go: an agent searches issues by JQL, runs sprints, comments and worklogs and sees an issue's branches and pull requests on Cloud and Server

MCP serverBroad access96

redmine-cli runs Redmine issues and time tracking from a terminal and exposes them to agents as a skill or MCP server

CLIExtended access63

Linear CLI

linear-cli

A Linear CLI for the terminal: list, start and create issues, PRs from a branch, JSON output and an agent skill, with git and jj support

CLIBroad access1K

Official Todoist command line with an agent skill: tasks, projects and inbox from the terminal

CLIExtended access332

Linearis manages Linear issues and projects from the terminal, returns JSON and exposes focused command references to agents.

CLIExtended access265

README in short

For a local Jira installation, `basic` uses a username and password, while `bearer` uses a personal access token. `mtls` is configured with a client certificate and key plus a CA certificate.

README badge

Report a problem