This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description
What is this
============

This (simple) script aimed to manage JIRA issues. It designed to be
used from scripts and accept all details via CLI.

To reduce typing one may use configuration file(s) to specify reusable
parameters. A sample config file provided in `/etc/jira-bot/`.
For initial system-wide setup rename `jira-bot.conf.sample` to `jira-bot.conf`
or copy it to user home directory as `.jira-botrc`. Then edit values according
your needs. Here is a sample configuration file. You need to replace values in
angle brackets to your data:


[default]
server=https://<jira-server>
verbose=1

[https://<jira-server>]
username=<login>
password=<pass>
project=<default-project-name>

[http://<another-jira-server>]


Note, that system-wide and per user config files are **additive** -- that means
you can specify _default server_ in system-wide config, and particular credentials
at `.jira-botrc` **at same section**.

Default server (i.e. when `--server` CLI option is omitted) would be taken from
`default` section of config file. **Per user configuration will take precedence
over the system-wide, but CLI options always win**.

Usage examples:

# Create a new issue using pipe
$ echo 'Bug description...' | jira-bot -v create -s 'Bug summary' -t Bug -f attach.file.1 attach.file.2

# Create a new issue using file w/ description
$ jira-bot create -s 'Proposal summary' -t 'New Feature' -f attach.file.1 attach.file.2 -- description.txt

# Change summary and priority of existed issue
$ jira-bot update -i EXISTED-123 -s 'New summary' -p Trivial

# Add comment visible to developers
$ jira-bot comment -i ISSUE-456 add -v Developers < comment-content.txt

# Brief list of comments
$ jira-bot comment -i ISSUE-456 ls
Release History

Release History

2.0.1

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting