gem-hunter
Language: Go
🔥 Feature-rich interactive Jira command line.
Feature-rich Interactive Jira Command Line
Financial support from private and corporate sponsors ensures the tool's continued development.
Please consider sponsoring the project if you or your company rely on JiraCLI.
JiraCLI is an interactive command line tool for Atlassian Jira that will help you avoid using the Jira UI to some extent. This tool may not be able to do everything, but it has all the essential features required to improve your day-to-day workflow with Jira.
The tool started with the idea of making issue search and navigation as straightforward as possible. However, with the help of outstanding supporters like you, we evolved, and the tool now includes all necessary features like issue creation, cloning, linking, ticket transition, and much more.
This tool is heavily inspired by the GitHub CLI
Note
Some features might work slightly differently in Jira Cloud versus on-premises installations due to the nature of the data. Yet, we've attempted to make the experience as similar as possible.
| Platform | |
|---|---|
| Jira |
SKILL.md ← for agents
JiraCLI works well with LLM-powered CLI tools like Claude Code, Codex, OpenCode, as well as shell-based automation.
jira-cli is available as a downloadable packaged binary for Linux, macOS, and Windows from the releases page.
You can use Docker to quickly try out jira-cli.
docker run -it --rm ghcr.io/ankitpokhrel/jira-cli:latest
Follow the installation guide for other installation methods like Homebrew, Nix, etc.
JIRA_API_TOKEN variable. Add it to your shell configuration file, for instance, $HOME/.bashrc, so that the
variable is always available. Alternatively, you can also use .netrc file or keychain to set the token. Learn
more here.jira init, select installation type as Cloud, and provide required details to generate a config file required
for the tool.password you use to login to Jira as a JIRA_API_TOKEN variable.token from your Jira profile and export it as
a JIRA_API_TOKEN variable. In addition to this, set JIRA_AUTH_TYPE env to bearer.$HOME/.bashrc, so that they are always available..netrc file or keychain to set the token. Learn
more here.jira init, select installation type as Local, and provide the required details to generate a config file required
for the tool.
basic. If you are using your Jira login credentials
(username and password), select the basic auth type.mtls (client certificates), select auth type mtls and provide the CA Cert, client Key, and client cert.Important
If your on-premises Jira installation is using a language other than English, then the issue/epic creation
may not work because the older version of Jira API doesn't return the untranslated name for issuetypes. In that case,
you will have to fill in epic.name, epic.link and issue.types.*.handle fields manually in the generated config
to get the expected behavior.
See FAQs for frequently asked questions.
The tool supports basic, bearer (Personal Access Token), and mtls (Client Certificates) authentication types. Basic auth is used by
default.
JIRA_AUTH_TYPE as bearer.mtls run jira init. Select installation type Local, and then select authentication type as mtls.
JIRA_API_TOKEN variable is set it will be used together with mtls.Check jira completion --help for more info on setting up a Bash/Zsh shell completion.
You can load a specific configuration file by using the --config/-c flag, or by setting the JIRA_CONFIG_FILE environment variable to specify the file's location.
$ JIRA_CONFIG_FILE=./local_jira_config.yaml jira issue list
# Alternatively, use the `--config/-c` flag
$ jira issue list -c ./local_jira_config.yamlThe tool currently comes with an issue, epic, and sprint explorer. The flags are POSIX-compliant.
You can combine available flags in any order to create a unique query. For example, the command below will give you high priority issues created this month
with status To Do that are assigned to you and has the label backend.
jira issue list -yHigh -s"To Do" --created month -lbackend -a$(jira me)
The lists are displayed in an interactive UI by default.
j, k, h, l characters to navigate through the list.g and G to quickly navigate to the top and bottom respectively.CTRL + f to scroll through a page downwards direction.CTRL + b to scroll through a page in upwards direction.v to view selected issue details.m to transition the selected issue.CTRL + r or F5 to refresh the issues list.ENTER to open the selected issue in the browser.c to copy issue URL to the system clipboard. This requires xclip / xsel on Linux.CTRL + k to copy issue key to the system clipboard.w or TAB to toggle focus between the sidebar and the contents screen.q / ESC / CTRL + c to quit.? to open the help window.Issues are displayed in an interactive table view by default. You can output the results in a plain view using the --plain flag.
The list command lets you search and navigate the issues. The issues are sorted by created field in descending order by default.
# List recent issues $ jira issue list # List issues created in last 7 days $ jira issue list --created -7d # List issues in status "To Do" $ jira issue list -s"To Do" # List recent issues in plain mode $ jira issue list --plain # List recent issues in raw JSON format $ jira issue list --raw # List recent issues in csv format $ jira issue list --csv # List issue in the same order as you see in the UI $ jira issue list --order-by rank --reverse # You can execute raw JQL within a given project context using `--jql/-q` option. # For instance, the following command will list issues in the current project whose # summary has a word cli. $ jira issue list -q "summary ~ cli"
Check some more examples/use-cases below.
List issues that I am watchingjira issue list -w
jira issue list -a$(jira me)jira issue list -a"User A" -r"User B"
jira issue list -a$(jira me) -yHigh -sopenjira issue list -ax --created week
jira issue list -R"Won't do"# Tilde (~) acts as a not operator
jira issue list -s~Done --created-before -24w -a~xjira issue list --created -1h --updated -30m
jira issue list -yHigh -s"In Progress" --created month -lbackend -l"high-prio"
jira issue list --history
jira issue list -r$(jira me) --reversejira issue list -a$(jira me) -tBug -sDone -rFixed --reversejira issue list -r$(jira me) --created weekjira issue list -w -pXYZ
The create command lets you create an issue.
# Create an issue using an interactive prompt $ jira issue create # Pass required parameters and use --no-input option to skip prompt $ jira issue create -tBug -s"New Bug" -yHigh -lbug -lurgent -b"Bug description" --fix-version v2.0 --no-input
To attach epic to an issue on creation, you can use -P/--parent field. We call it parent because the semantics of epic
has been changed in next-gen project.
# Create an issue of type Story and attach it to epic with key EPIC-42 $ jira issue create -tStory -s"Epic during creation" -PEPIC-42
You can use a --custom flag to set custom fields while creating the issue. See this post for more details.
The command supports both GitHub-flavored
and Jira-flavored Markdown for writing
description. You can load pre-defined templates using --template flag.
# Load description from template file $ jira issue create --template /path/to/template.tmpl # Get description from standard input $ jira issue create --template - # Or, use pipe to read input directly from standard input $ echo "Description from stdin" | jira issue create -s"Summary" -tTask
The preview above shows a Markdown template passed in JiraCLI and how it is rendered in the Jira UI.
The edit command lets you edit an issue.
$ jira issue edit ISSUE-1 # Edit issue in the configured project $ jira issue edit ISSUE-1 -s"New Bug" -yHigh -lbug -lurgent -CBackend -b"Bug description" # Use --no-input option to disable interactive prompt $ jira issue edit ISSUE-1 -s"New updated summary" --no-input # Use minus (-) to remove label, component or fixVersion # For instance, to edit issue to # - remove label p2, component FE, fixVersion v1.0 # - add label p1, component BE, fixVersion v2.0 $ jira issue edit ISSUE-1 --label -p2 --label p1 --component -FE --component BE --fix-version -v1.0 --fix-version v2.0
The assign command lets you assign a user to an issue.
# Assign user to an issue using an interactive prompt $ jira issue assign # Pass required parameters to skip prompt $ jira issue assign ISSUE-1 "Jon Doe" # Assign to self $ jira issue assign ISSUE-1 $(jira me) # Will prompt for selection if keyword suffix returns multiple entries $ jira issue assign ISSUE-1 suffix # Assign to default assignee $ jira issue assign ISSUE-1 default # Unassign $ jira issue assign ISSUE-1 x
The move command lets you transition an issue from one state to another.
# Move an issue using an interactive prompt $ jira issue move # Pass required parameters to skip prompt $ jira issue move ISSUE-1 "In Progress"
If your workflow allows to add comment, resolution or assignee while moving an issue, you can do so as shown below. See this documentation on how to setup your workflow to allow these fields.
# Move an issue and add comment $ jira issue move ISSUE-1 "In Progress" --comment "Started working on it" # Set resolution to fixed and assign to self while moving the issue $ jira issue move ISSUE-1 Done -RFixed -a$(jira me)
To transition the selected issue from the TUI, press m.
The view command lets you see issue details in a terminal. Atlassian document is roughly converted to Markdown
and is nicely displayed in the terminal.
The command uses less as a pager by default. To set your own pager, see #569.
$ jira issue view ISSUE-1
The view screen will display linked issues and the latest comment after the description. Note that the displayed comment may not be the latest one if you for some reason have more than 5k comments in a ticket.
# Show 5 recent comments when viewing the issue
$ jira issue view ISSUE-1 --comments 5The link command lets you link two issues.
# Link an issue using an interactive prompt $ jira issue link # Pass required parameters to skip prompt $ jira issue link ISSUE-1 ISSUE-2 Blocks
The remote command lets you add a remote web link to an issue.
# Adds a remote web link using an interactive prompt $ jira issue link remote # Pass required parameters to skip prompt $ jira issue link remote ISSUE-1 https://example.com "Example text"
The unlink command lets you unlink two linked issues.
# Unlink issues using interactive prompt $ jira issue unlink # Pass required parameters to skip prompt $ jira issue unlink ISSUE-1 ISSUE-2
The clone command lets you clone an issue. You can update fields like summary, priority, assignee, labels, and
components when cloning the issue. The command also allows you to replace a part of the string (case-sensitive)
in summary and description using --replace/-H option.
# Clone an issue $ jira issue clone ISSUE-1 # Clone issue and modify the summary, priority and assignee $ jira issue clone ISSUE-1 -s"Modified summary" -yHigh -a$(jira me) # Clone issue and replace text from summary and description $ jira issue clone ISSUE-1 -H"find me:replace with me"
The delete command lets you delete an issue.
# Delete an issue using an interactive prompt $ jira issue delete # Pass required parameters to skip prompt $ jira issue delete ISSUE-1 # Delete task along with all of its subtasks $ jira issue delete ISSUE-1 --cascade
The comment command provides a list of sub-commands to manage issue comments.
The add command lets you add a comment to an issue. The command supports both GitHub-flavored
and Jira-flavored Markdown for writing
comment. You can load pre-defined templates using --template flag.
# Add a comment using an interactive prompt $ jira issue comment add # Pass required parameters to skip prompt $ jira issue comment add ISSUE-1 "My comment body" # Same as above but as an internal comment $ jira issue comment add ISSUE-1 "My comment body" --internal # Load comment from template file $ jira issue comment add ISSUE-1 --template /path/to/template.tmpl # Get comment from standard input $ jira issue comment add ISSUE-1 --template - # Or, use pipe to read input directly from standard input $ echo "Comment from stdin" | jira issue comment add ISSUE-1
Note
For the comment body, the positional argument always takes precedence over the --template flag if both of them are passed. In the
example below, the body will be picked from positional argument instead of the template.
jira issue comment add ISSUE-42 "comment body positional" --template - <<'EOF' comment body template EOF
The worklog command provides a list of sub-commands to manage issue worklog (timelog).
The add command lets you add a worklog to an issue. The command supports Markdown for worklog comments.
# Add a worklog using an interactive prompt $ jira issue worklog add # Pass required parameters and use --no-input to skip prompt $ jira issue worklog add ISSUE-1 "2d 3h 30m" --no-input # You can add a comment using --comment flag when adding a worklog $ jira issue worklog add ISSUE-1 "10m" --comment "This is a comment" --no-input
Epics are displayed in an explorer view by default. You can output the results in a table view using the --table flag.
When viewing epic issues, you can use all filters available for the issue command.
See usage to learn more about UI interaction.
You can use all flags supported by issue list command here except for the issue type.
# List epics $ jira epic list # List epics in a table view $ jira epic list --table # List epics reported by me and are open $ jira epic list -r$(jira me) -sOpen # List issues in an epic $ jira epic list KEY-1 # List all issue in an epic KEY-1 that is unassigned and has a high priority $ jira epic list KEY-1 -ax -yHigh # List high priority epics $ jira epic list KEY-1 -yHigh # List epic issues ordered by rank in ascending order $ jira epic list KEY-1 --order-by rank --reverse
Creating an epic is the same as creating the issue except you also need to provide an epic name.
# Create an issue using an interactive prompt $ jira epic create # Pass required parameters to skip prompt or use --no-input flag to skip prompt for non-mandatory params $ jira epic create -n"Epic epic" -s"Everything" -yHigh -lbug -lurgent -b"Epic description"
The add command allows you to add issues to the epic. You can add up to 50 issues to the epic at once.
# Add issues to the epic using an interactive prompt $ jira epic add # Pass required parameters to skip prompt $ jira epic add EPIC-KEY ISSUE-1 ISSUE-2
The remove command allows you to remove issues from the epic. You can remove up to 50 issues from the epic at once.
# Remove issues to the epic using an interactive prompt $ jira epic remove # Pass required parameters to skip prompt $ jira epic remove ISSUE-1 ISSUE-2
Sprints are displayed in an explorer view by default. You can output the results in a table view using the --table flag.
When viewing sprint issues, you can use all filters available for the issue command. The tool only shows 25 recent sprints.
See usage to learn more about UI interaction.
You can use all flags supported by issue list command to filter issues in the sprint.
# List sprints in an explorer view $ jira sprint list # List sprints in a table view $ jira sprint list --table # List issues in the current active sprint $ jira sprint list --current # List issues in the current active sprint that are assigned to me $ jira sprint list --current -a$(jira me) # List issues in the previous sprint $ jira sprint list --prev # List issues in next planned sprint $ jira sprint list --next # List future and active sprints $ jira sprint list --state future,active # List issues in a particular sprint. You can use all flags supported by issue list command here. # To get sprint id use `jira sprint list` or `jira sprint list --table` $ jira sprint list SPRINT_ID # List high priority issues in a sprint are assigned to me $ jira sprint list SPRINT_ID -yHigh -a$(jira me) # List sprint issues ordered by rank in ascending order $ jira sprint list SPRINT_ID --order-by rank --reverse
The add command allows you to add issues to the sprint. You can add up to 50 issues to the sprint at once.
# Add issues to the sprint using interactive prompt $ jira sprint add # Pass required parameters to skip prompt $ jira sprint add SPRINT_ID ISSUE-1 ISSUE-2
Interact with releases (project versions).
Ensure the feature is enabled on your instance.
# List releases for default project $ jira release list # List releases for specific project $ jira release list --project 1000 $ jira release list --project KEY
jira open
jira open KEY-1
jira project list
jira board list
Often times, you may want to use the output of the command to do something cool. However, the default interactive UI might not allow you to do that.
The tool comes with the --plain flag that displays results in a simple layout that can then be manipulated from the shell script.
Some example scripts are listed below.
Tickets created per day this month#!/usr/bin/env bash tickets=$(jira issue list --created month --plain --columns created --no-headers | awk '{print $2}' | awk -F'-' '{print $3}' | sort -n | uniq -c) echo "${tickets}" | while IFS=$'\t' read -r line; do day=$(echo "${line}" | awk '{print $2}') count=$(echo "${line}" | awk '{print $1}') printf "Day #%s: %s\n" "${day}" "${count}" done # Output Day #01: 19 Day #02: 10 Day #03: 21 ...
#!/usr/bin/env bash sprints=$(jira sprint list --table --plain --columns id,name --no-headers) echo "${sprints}" | while IFS=$'\t' read -r id name; do count=$(jira sprint list "${id}" --plain --no-headers 2>/dev/null | wc -l) printf "%10s: %3d\n" "${name}" $((count)) done # Output Sprint 3: 55 Sprint 2: 40 Sprint 1: 30 ...
#!/usr/bin/env bash sprints=$(jira sprint list --table --plain --columns id,name --no-headers) echo "${sprints}" | while IFS=$'\t' read -r id name; do count=$(jira sprint list "${id}" --plain --columns assignee --no-headers 2>/dev/null | awk '{print $2}' | awk NF | sort -n | uniq | wc -l) printf "%10s: %3d\n" "${name}" $((count)) done # Output Sprint 3: 5 Sprint 2: 4 Sprint 1: 3
Please open a discussion in ideas category for the proposed feature.
Clone the repo.
git clone git@github.com:ankitpokhrel/jira-cli.git
Optional: If you want to run a Jira instance locally, you can use the following make recipe. The trial license key can be generated from the "Licenses" section in the Atlassian admin.
make jira.server
Make changes, build the binary, and test your changes.
make deps install
Run CI steps locally before submitting a PR.
make ci
Your suggestions and feedbacks are highly appreciated. Please feel free to start a discussion or create an issue to share your experience with the tool or to discuss a feature/issue.
If you think this tool is useful, saves you a lot of work, and lets you sleep much better, then consider supporting the project by any of the following means:
Made with 💚