{"_id":"@amritghimire/jira-terminal","name":"@amritghimire/jira-terminal","dist-tags":{"latest":"2.5.0"},"versions":{"2.5.0":{"artifactDownloadUrls":["https://github.com/amritghimire/jira-terminal/releases/download/v2.5.0"],"author":{"name":"Amrit Ghimire","email":"iamritghimire@gmail.com"},"bin":{"jira-terminal":"run-jira-terminal.js"},"dependencies":{"axios":"^1.13.5","axios-proxy-builder":"^0.1.2","console.table":"^0.10.0","detect-libc":"^2.1.2","rimraf":"^6.1.3"},"description":"This is a command line application that can be used as a personal productivity tool for interacting with JIRA","devDependencies":{"prettier":"^3.8.1"},"engines":{"node":">=14","npm":">=6"},"glibcMinimum":{"major":2,"series":35},"homepage":"https://github.com/amritghimire/jira-terminal","keywords":["command-line-utilities","jira","terminal","command-line"],"license":"AGPL-3.0-only","name":"@amritghimire/jira-terminal","preferUnplugged":true,"repository":{"type":"git","url":"git+https://github.com/amritghimire/jira-terminal.git"},"scripts":{"fmt":"prettier --write **/*.js","fmt:check":"prettier --check **/*.js","postinstall":"node ./install.js"},"supportedPlatforms":{"aarch64-apple-darwin":{"artifactName":"jira-terminal-aarch64-apple-darwin.tar.gz","bins":{"jira-terminal":"jira-terminal"},"zipExt":".tar.gz"},"aarch64-pc-windows-msvc":{"artifactName":"jira-terminal-x86_64-pc-windows-msvc.tar.gz","bins":{"jira-terminal":"jira-terminal.exe"},"zipExt":".tar.gz"},"x86_64-apple-darwin":{"artifactName":"jira-terminal-x86_64-apple-darwin.tar.gz","bins":{"jira-terminal":"jira-terminal"},"zipExt":".tar.gz"},"x86_64-pc-windows-gnu":{"artifactName":"jira-terminal-x86_64-pc-windows-msvc.tar.gz","bins":{"jira-terminal":"jira-terminal.exe"},"zipExt":".tar.gz"},"x86_64-pc-windows-msvc":{"artifactName":"jira-terminal-x86_64-pc-windows-msvc.tar.gz","bins":{"jira-terminal":"jira-terminal.exe"},"zipExt":".tar.gz"},"x86_64-unknown-linux-gnu":{"artifactName":"jira-terminal-x86_64-unknown-linux-gnu.tar.gz","bins":{"jira-terminal":"jira-terminal"},"zipExt":".tar.gz"},"x86_64-unknown-linux-musl-dynamic":{"artifactName":"jira-terminal-x86_64-unknown-linux-musl.tar.gz","bins":{"jira-terminal":"jira-terminal"},"zipExt":".tar.gz"},"x86_64-unknown-linux-musl-static":{"artifactName":"jira-terminal-x86_64-unknown-linux-musl.tar.gz","bins":{"jira-terminal":"jira-terminal"},"zipExt":".tar.gz"}},"version":"2.5.0","volta":{"node":"18.14.1","npm":"9.5.0"},"_id":"@amritghimire/jira-terminal@2.5.0","bugs":{"url":"https://github.com/amritghimire/jira-terminal/issues"},"_integrity":"sha512-9KU6wmLHv6zZ0krVhweCGoPJOeRPfPcnO9Oi10dmQhJNw2B5ULCPP0w2rdO8CaROPntgW/gHylynrRHmeN69CQ==","_resolved":"/home/runner/work/jira-terminal/jira-terminal/npm/jira-terminal-npm-package.tar.gz","_from":"file:npm/jira-terminal-npm-package.tar.gz","_nodeVersion":"20.20.0","_npmVersion":"10.8.2","dist":{"integrity":"sha512-9KU6wmLHv6zZ0krVhweCGoPJOeRPfPcnO9Oi10dmQhJNw2B5ULCPP0w2rdO8CaROPntgW/gHylynrRHmeN69CQ==","shasum":"dea17916e13b612d3ec71f931ef3dc55f13164bb","tarball":"https://registry.npmjs.org/@amritghimire/jira-terminal/-/jira-terminal-2.5.0.tgz","fileCount":10,"unpackedSize":77188,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEYCIQCETgS9ksAma1J4mnIHqUffuQoWkuiilMVbb/SYgzIkdwIhAIyALrwenIWqyGdPXPB6lK318bBhsxTN0r5S1EPvwQol"}]},"_npmUser":{"name":"iamritghimire","email":"iamritghimire@gmail.com"},"directories":{},"maintainers":[{"name":"iamritghimire","email":"iamritghimire@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/jira-terminal_2.5.0_1773202232677_0.6154448434577036"},"_hasShrinkwrap":true}},"time":{"created":"2026-03-11T04:10:32.333Z","2.5.0":"2026-03-11T04:10:32.837Z","modified":"2026-03-11T04:10:33.018Z"},"maintainers":[{"name":"iamritghimire","email":"iamritghimire@gmail.com"}],"description":"This is a command line application that can be used as a personal productivity tool for interacting with JIRA","homepage":"https://github.com/amritghimire/jira-terminal","keywords":["command-line-utilities","jira","terminal","command-line"],"repository":{"type":"git","url":"git+https://github.com/amritghimire/jira-terminal.git"},"author":{"name":"Amrit Ghimire","email":"iamritghimire@gmail.com"},"bugs":{"url":"https://github.com/amritghimire/jira-terminal/issues"},"license":"AGPL-3.0-only","readme":"## Jira Terminal\n\nThis application can be used for personal usage to manage jira from terminal.\n\n## Installation\n\nThis application can be used in multiple platform.\n\n### MacOS\n\nThis package is available in brew as `jira-terminal`. You can install it with following command:\n\n```\nbrew tap amritghimire/jira-terminal \nbrew install jira-terminal\n```\n\n### Arch Linux\n\nThis package is available in aur repository as [jira-terminal-bin](https://aur.archlinux.org/packages/jira-terminal-bin/)\n\n### Debian/Ubuntu\n\nOn debian based system, the deb file is available in [releases](https://github.com/amritghimire/jira-terminal/releases). You can download latest release from there. Please make sure libc is installed in your system.\n\n### Cargo\n\nIf you already have a Rust environment set up, you can use the cargo install command:\n```cargo install jira-terminal```\n\nCargo will build the jira-terminal binary and place it in $HOME/.cargo/bin.\nYou can also setup Rust toolchain from [Rust official site](https://www.rust-lang.org/tools/install)\n\n### Manual Installation from Github\n\nCompiled binary versions of jira-terminal are uploaded to GitHub when a release is made. You can install jira-terminal manually by [downloading a release](https://github.com/amritghimire/jira-terminal/releases) , extracting it, and copying the binary to a directory in your $PATH, such as /usr/local/bin.\n\n## Autocompletion Script\n\nThe autocompletion script can be found in [the release section](https://github.com/amritghimire/jira-terminal/releases).\nYou can download the autocompletion script from there or use our application to generate the script.\nTo generate the script, run:\n\n```bash\njira-terminal autocompletion --shell [zsh|bash|fish|powershell|elvish] > _jira.terminal\n```\n\nDepending on your shell, you can move your autocompletion file to the following location:\n\n- *ZSH* - `/usr/share/zsh/site-functions/_jira-terminal`\n- *BASH* - `/usr/share/bash-completion/completions/_jira-terminal`\n- *Fish* - `/share/fish/vendor_completions.d/_jira-terminal`\n\n## Usage\n\nWhen running the application for first time, you will be asked with following values.\n\n- hostname [This will be used to identify the jira hostname to be used.]\n- email [Email address you use to login with the application.]\n- token [You can obtain the app password from the link specified in the application]\n\nAfter that, you can use following commands for help.\n\n```\njira-terminal help\njira-terminal help list\njira-terminal help transition\njira-terminal help alias\njira-terminal help detail\njira-terminal help fields\njira-terminal help update\njira-terminal help new\njira-terminal help assign\njira-terminal help comment\njira-terminal help autocompletion\njira-terminal help config\n```\n\n```\nJIRA Terminal 2.0.0\nAmrit Ghimire <oss@amritghimire.com>\nThis is a command line application that can be used as a personal productivity tool for interacting with JIRA\n\nUSAGE:\n    jira-terminal [SUBCOMMAND]\n\nFLAGS:\n    -h, --help       Prints help information\n    -V, --version    Prints version information\n\nSUBCOMMANDS:\n    alias             Configuration for alias. One of add,list or remove is required.\n    assign            Assign a ticket to user.\n    autocompletion    Generate autocompletion script..\n    comment           List or add comments to a ticket. Default action is adding.\n    config            Update configuration values.\n    detail            Detail of a JIRA tickets..\n    fields            List of possible Fields for details...\n    help              Prints this message or the help of the given subcommand(s)\n    list              List the issues from JIRA.\n    new               Create a new ticket.\n    transition        Transition of ticket across status.\n    update            Update a field for a ticket\n    logout            Erase configuration and log out of Jira\n```\n\n### List of Tickets\n\n```\n\njira-terminal-list \nList the issues from JIRA.\n\nUSAGE:\n    jira-terminal list [FLAGS] [OPTIONS]\n\nFLAGS:\n    -h, --help       Prints help information\n    -J, --json       JSON response\n    -M, --me         Issues assigned to you.\n    -V, --version    Prints version information\n\nOPTIONS:\n    -A, --alias <ALIAS>               Save the applied options as an alias. You can use it with jql option later.\n    -a, --assignee <ASSIGNEE>...       Assignee username or email to filter with.\n    -c, --component <COMPONENT>...    Component name or ID to filter with.\n    -C, --count <COUNT>               Total number of issues to show. (Default is 50)\n    -d, --display <DISPLAY>            Comma separated list of fields to display.\n                                      Possible options for fields are:\n                                      key,resolution,priority,assignee,status,components,creator,reporter,issuetype,project,summary\n                                      \n                                      You can pass alias as option for display. You can save alias using alias\n                                      subcommand for the application.\n                                      \n                                       Default options are\n                                       key,summary,status,assignee\n                                                         \n    -e, --epic <EPIC>...              EPIC name or issue key of epic to filter with.\n    -f, --filter <FILTER>...          Filter name or filter id that you saved in JIRA.\n    -j, --jql <JQL>                   JQL Query or alias to JQL query to filter with.\n    -l, --label <LABEL>...            Search for issues with a label or list of labels.\n    -o, --offset <OFFSET>             Offset to start the first item to return in a page of results. (Default is 0)\n    -m, --main <PARENT>...            Search for subtask of a particular issue.\n    -P, --priority <PRIORITY>...      Search for issues with a particular priority.\n    -p, --project <PROJECT>...        Project Code to filter with.\n    -r, --reporter <REPORTER>...      Search for issues that were reported by a particular user.\n    -s, --sprint <SPRINT>...          Search for issues that are assigned to a particular sprint.\n    -S, --status <STATUS>...          Search for issues that have a particular status.\n    -T, --text <TEXT>                 This is a master-field that allows you to search all text fields for issues.\n    -t, --type <TYPE>...              Search for issues that have a particular issue type. \n\nYou can specify the following fields multiple time to filter by multiple values.\nassignee, component, epic, filter, label, main, priority, project, reporter, sprint, status, type.\n\nFor example to fetch list of tickets in Backlog and In progress, you can use\njira-terminal list -s Backlog -s 'In Progress'\n```\n\n### Transition\n\n```\njira-terminal-transition \nTransition of ticket across status.\n\nUSAGE:\n    jira-terminal transition [FLAGS] <STATUS> --ticket <TICKET>\n\nFLAGS:\n    -h, --help       Prints help information\n    -l, --list       List the possible transitions.\n    -V, --version    Prints version information\n\nOPTIONS:\n    -t, --ticket <TICKET>    Ticket ID from JIRA.\n\nARGS:\n    <STATUS>    Status or alias of status to move the ticket to.\n\n```\n\n### Alias\n\n```\njira-terminal-alias \nConfiguration for alias. One of add,list or remove is required.\n\nUSAGE:\n    jira-terminal alias [FLAGS] <NAME> --add <add> --list --remove\n\nFLAGS:\n    -h, --help       Prints help information\n    -l, --list       List the alias saved.\n    -r, --remove     List the alias saved.\n    -V, --version    Prints version information\n\nOPTIONS:\n    -a, --add <add>    Value to associate with provided alias name.\n\nARGS:\n    <NAME>    Name of alias. (Required except for list option)\n```\n\nSample usage:\n\n- `jira-terminal alias -l`\n- `jira-terminal alias alias_name -a \"Alias Value\"`\n- `jira-terminal alias -r alias_name`\n\n### Detail\n\n```\njira-terminal-detail \nDetail of a JIRA tickets..\n\nUSAGE:\n    jira-terminal detail [OPTIONS] <TICKET>\n\nFLAGS:\n    -h, --help       Prints help information\n    -V, --version    Prints version information\n\nOPTIONS:\n    -f, --fields <fields>    Comma separated lists of fields or alias to show.\n                             Possible options are: \n                             key,summary,description,status,issuetype,priority,labels,assignee,components,creator,reporter,project,comment\n                             \n                             You can use all to show all fields.\n                             Default selection are:\n                             key,summary,description\n                                                 \n\nARGS:\n    <TICKET>    Ticket id for details.\n\n```\n\n### Fields\n\n```\njira-terminal-fields \nList of possible Fields for details...\n\nUSAGE:\n    jira-terminal fields <TICKET>\n\nFLAGS:\n    -h, --help       Prints help information\n    -V, --version    Prints version information\n\nARGS:\n    <TICKET>    Ticket id for details.\n```\n\n### Update\n\n```\njira-terminal-update \nUpdate a field for a ticket\n\nUSAGE:\n    jira-terminal update <TICKET> --field <field> --value <value>\n\nFLAGS:\n    -h, --help       Prints help information\n    -V, --version    Prints version information\n\nOPTIONS:\n    -f, --field <field>    Key of field to update. You can use jira-terminal fields <TICKET> to see possible set of\n                           keys.\n    -v, --value <value>    Value of the field to update.\n\nARGS:\n    <TICKET>    Ticket ID to update\n```\n\n### New\n\n```\njira-terminal-new \nCreate a new ticket.\n\nUSAGE:\n    jira-terminal new [FLAGS] [OPTIONS] --main <main> --project <project>\n\nFLAGS:\n    -h, --help       Prints help information\n    -M, --minimal    Only summary and description will be asked if not available.\n    -q, --quiet      Do not ask for missing options.\n    -V, --version    Prints version information\n\nOPTIONS:\n    -a, --assignee <assignee>          Assignee email of ticket\n    -c, --components <components>      Comma separated list of components of ticket\n    -C, --custom <custom>              Comma separated value pair for custom fields. You can use alias in value or key\n                                       itself. Example- \"customfield_12305:value,alias_to_key:value2. You can use fields\n                                       subcommand to check the list of custom fields available. \n    -d, --description <description>    Description of ticket\n    -l, --labels <labels>              Comma separated list of labels.\n    -m, --main <main>                  Main ticket to create the sub-ticket.\n    -p, --priority <priority>          Priority Of the ticket.\n    -P, --project <project>            Project Key to create the ticket.\n    -s, --summary <summary>            Summary of ticket\n    -t, --type <type>                  Issue type for new ticket.\n```\n\n### Assign\n\n```\njira-terminal-assign \nAssign a ticket to user.\n\nUSAGE:\n    jira-terminal assign --ticket <ticket> --user <user>\n\nFLAGS:\n    -h, --help       Prints help information\n    -V, --version    Prints version information\n\nOPTIONS:\n    -t, --ticket <ticket>    Ticket to use.\n    -u, --user <user>        Assign the ticket to the provided user.\n```\n\n### Comment\n\n```\njira-terminal-comment \nList or add comments to a ticket. Default action is adding.\n\nUSAGE:\n    jira-terminal comment [FLAGS] [OPTIONS] --ticket <ticket>\n\nFLAGS:\n    -h, --help       Prints help information\n    -l, --list       List all the comments of a ticket.\n    -V, --version    Prints version information\n\nOPTIONS:\n    -b, --body <body>        Body of the comment. To mention someone, you can use @(query) The query can include jira\n                             username or display name or email address.\n    -t, --ticket <ticket>    Ticket to use.\n```\n\n### Config\n\n```\njira-terminal-config \nUpdate configurations. \n\nUSAGE:\n    jira-terminal config [FLAGS] <key> <value>\n\nFLAGS:\n    -h, --help       Prints help information\n    -V, --version    Prints version information\n\n```\n\n## Notes\n\n- The credentials and other configuration are stored following the XDG Base Directory specification:\n  - **Linux**: `$XDG_CONFIG_HOME/jira-terminal/configuration.json` (default: `~/.config/jira-terminal/configuration.json`)\n  - **macOS**: `~/Library/Application Support/jira-terminal/configuration.json`\n  - **Windows**: `%APPDATA%\\jira-terminal\\configuration.json`\n- The base64 encoded version of credentials are only written in the configuration file.\n- If upgrading from an older version, your config will be automatically migrated from `~/.jira_terminal_configuration.json` to the new location on first run.\n","readmeFilename":"README.md","_rev":"1-5ff4e0352c8066d427f20848220f93f1"}