grdev.jira-cli 0.1.56

jira-cli

jira is a command-line tool for reading and writing issues in Jira Cloud.

Project page: greekdeveloper.com/tools/jira-cli

Install

dotnet tool install --global grdev.jira-cli

What it can do

• See your open issues — jira issue list lists issues for the saved default query (open issues assigned to you, until you change it)
• Filter with JQL — jira issue list --jql "project = ABC AND status = 'In Progress'" runs any JQL directly, or pass --query <name> for one you've saved
• Save queries for reuse — jira query add mine --description "..." --query "...", then jira issue list --query mine. jira query list shows what's saved
• Walk a hierarchy — add --include-children to any issue list/tree/stats query to also pull in every issue below the ones it matches, all the way down the parent/sub-task chain: jira issue tree --jql "key = EPIC-1" --include-children
• Look at one issue — jira issue show ABC-123 prints its title, project, status, labels, assignee, transitions, related issues, description, and comments
• Create issues — jira issue create -p ABC -s "Fix the thing" files a new one; save reusable presets with jira template add <name> ... and apply them with --template <name>
• Move issues along — jira issue transition ABC-123 "In Progress" applies a workflow transition, jira issue assign ABC-123 [email] reassigns one, and jira issue open ABC-123 opens it in the browser

Commands follow a noun verb structure (jira issue list, jira issue show, jira issue create, jira query add, jira template add). Run jira --help to explore.

Setup

jira profile add work --host https://your-site.atlassian.net --email you@example.com creates your first profile (the first one added becomes active automatically); jira config edit then opens config.json directly to fill in its ApiToken (an API token is never passed as a CLI flag). jira config path prints the file's location.

Every Jira site — its connection, saved queries, templates, and settings — lives in a named profile; jira profile add another one and jira profile use <name> to switch, or set JIRA_PROFILE=<name> for one command. config.json ends up shaped like:

{
  "Profiles": [
    {
      "Name": "work",
      "Connection": {
        "Host": "https://your-site.atlassian.net",
        "Email": "you@example.com",
        "ApiToken": "your-api-token"
      },
      "Queries": [],
      "Templates": [],
      "Settings": { "IncludeChildren": false }
    }
  ],
  "DefaultProfile": "work"
}

Settings.IncludeChildren (default false) makes --include-children the default for issue list/tree/stats on that site; pass --include-children false to switch it off for one command.

Generate an API token at https://id.atlassian.com/manage-profile/security/api-tokens

For contributors

Build steps, project layout, and conventions live in BRIEF.md. Agent and repository conventions live in AGENTS.md.

Versioning

Versions are computed by Nerdbank.GitVersioning from version.json plus the git height — every commit bumps the patch automatically. jira version reports the exact build and commit that is running.