Introduction

Simple command line utility to interact with your jira instance.

Installation

with easy_install or pip:

sudo easy_install jira-cli
sudo pip install jira-cli

from source (bitbucket repository):

hg clone http://hg.indydevs.org/jira-cli
cd jira-cli
python setup.py build
sudo python setup.py install

after installation, a few configuration steps will be prompted upon invoking jira-cli for the first time:
```
ali@home ~ $ jira-cli
base url for your jira instance (e.g http://issues.apache.org/jira):http://jira.yourdomain.com
enter username:ali
enter password:*********
```
The details of your jira instance will be kept in ~/.jira-cli/config and the authentication token will be stored in ~/.jira-cli/auth. Once the authentication token has expired you will be reprompted for your username & password again.

Usage

A few examples to get started.

create an issue with only a title in project TP with default priority and type Bug:

ali@home ~ $ jira-cli -n Bug -t "Test Bug" --priority=Major -p TP
link                 : http://jira.yourdomain.com/browse/TP-24
assignee             :
summary              : Test Bug
issue                : TP-24
reporter             : ali

create an issue with priority Major and a description:

ali@home ~ $ jira-cli -n Bug -t "Test Bug" --priority=Major -p TP the description
link                 : http://jira.yourdomain.com/browse/TP-25
assignee             :
summary              : Test Bug
issue                : TP-25
reporter             : ali

list the issue TP-25:

ali@home ~ $ jira-cli TP-25
link                 : http://jira.yourdomain.com/browse/TP-25
assignee             :
summary              : Test Bug
issue                : TP-25
reporter             : ali

list the issues TP-20 & TP-21:

ali@home ~ $ jira-cli TP-20 TP-21
link                 : http://jira.yourdomain.com/browse/TP-20
assignee             : ali
summary              : test
issue                : TP-20
reporter             : ali

link                 : http://jira.yourdomain.com/browse/TP-21
assignee             :
summary              : Test Bug
issue                : TP-21
reporter             : ali

list the issues in short form:

ali@home ~ $ jira-cli TP-20 TP-21 TP-22 --oneline
TP-20 test < http://jira.yourdomain.com/browse/TP-20 >
TP-21 Test Bug < http://jira.yourdomain.com/browse/TP-21 >
TP-22 Test Bug < http://jira.yourdomain.com/browse/TP-22 >

add a comment to an existing issue:

ali@home ~ $ jira-cli -j TP-20 -c this is a new comment
this is a new comment added to TP-20

provide your own formatting:

ali@home ~ $ jira-cli TP-20 --format="%reporter, %summary, %status"

Metadata

Release files for jira-cli 0.1.8-1-gd421df1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jira-cli 0.1.8-1-gd421df1
File	Size	Uploaded	Provenance	Actions
jira-cli-0.1.8-1-gd421df1.tar.gz	5.0 kB	Feb 23, 2012	Without provenance	Details for jira-cli-0.1.8-1-gd421df1.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for jira-cli 0.1.8-1-gd421df1
File	Interpreter	ABI	Platform	Actions Reset
jira_cli-0.1.8_1_gd421df1-py2.7.egg 9.7 kB Feb 23, 2012 Without provenance	Legacy Egg format	-	-	Details for jira_cli-0.1.8_1_gd421df1-py2.7.egg
jira_cli-0.1.8_1_gd421df1-py2.6.egg 9.7 kB Feb 23, 2012 Without provenance	Legacy Egg format	-	-	Details for jira_cli-0.1.8_1_gd421df1-py2.6.egg

Total release size: 24.4 kB

Release files / jira-cli-0.1.8-1-gd421df1.tar.gz

Download URL	jira-cli-0.1.8-1-gd421df1.tar.gz
Size	5.0 kB
Tags	Source
SHA-256 checksum How to use checksums	`7163323d37f713109483402b10decea0d1c0a0fee2aaa86ba1a1d695fd67ea5a`
BLAKE2b-256 checksum How to use checksums	`07de8f3b3960828eb6d61eb503fc40f0c50373ae84621e5b8a7840efd091af8a`
Upload date	Feb 23, 2012
Uploaded using Trusted Publishing? What is trusted publishing?	No

Release files / jira_cli-0.1.8_1_gd421df1-py2.7.egg

Download URL	jira_cli-0.1.8_1_gd421df1-py2.7.egg
Size	9.7 kB
Tags	Egg
SHA-256 checksum How to use checksums	`3502a569f912d84c342832fef0e0acd3e17fd6bbe5451f45f482ff5373d22233`
BLAKE2b-256 checksum How to use checksums	`08d8146d8f438c24a7eb79f3278db7bab0df677af634d0d0cfddb8d708f94e9c`
Upload date	Feb 23, 2012
Uploaded using Trusted Publishing? What is trusted publishing?	No

Release files / jira_cli-0.1.8_1_gd421df1-py2.6.egg

Download URL	jira_cli-0.1.8_1_gd421df1-py2.6.egg
Size	9.7 kB
Tags	Egg
SHA-256 checksum How to use checksums	`b9e4289540c5226dd12b77bde5c165a5687696d46278052bdcf532cd0dc02145`
BLAKE2b-256 checksum How to use checksums	`d0c417c5f5ccd4313798fe2765683410995bbe8ff065c906546c370c6abf50e9`
Upload date	Feb 23, 2012
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for jira-cli 0.1.8-1-gd421df1

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.