Skip to content

lusarz/jira-node-cli

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

61 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Love jira-node-cli? Please consider donating to sustain our activities

JIRA CLI   Build Status   Tweet

Usage: jira [options] [command] Options: -h, --help output usage information Commands: create-issue Create new issue issue-link [issueName] Copy issue link to clipboard issue-status [issueName] Show issue status issue [issueName] Show issue details jql [jql] Show issues using JQL all Alias => jira jql '' my-issues Alias => jira jql 'assignee in (currentUser()) ORDER BY status ASC' my-not-released Alias => jira jql 'status not in (Released) AND assignee in (currentUser()) ORDER BY status ASC' my-stage Alias => jira jql 'status in ('Deployed to Stage') AND assignee in (currentUser()) ORDER BY status ASC' sprint Alias => jira jql 'sprint in openSprints() ORDER BY status ASC' stage Alias => jira jql 'status in ('Deployed to Stage') ORDER BY status ASC' 

jira-all

jira-issue

Tips

Commands like jira all, jira my-not-released are implemented as aliases. I'm planning to allow user to create his own aliases but currently there is a few hardcoded, so you may meet error like:

JIRA respond with '400 Bad Request' status. ERROR MESSAGE: The value 'Released' does not exist for the field 'status'. Please try again later 

As a workaround please use plain jira jql queries, for example:

jira jql 'project=ABC AND status in (New)' jira jql 'assignee in (currentUser()) ORDER BY status ASC' jira jql 'project=XYZ AND assignee in (currentUser()) ORDER BY status ASC'	. 

Install

npm install -g jira-node-cli 

Usage

Type:

jira 

and you will be asked about credentials to your JIRA account. Credentials will be saved in ~/.jirarc file.

About

JIRA command line interface written in NodeJS

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors