Skip to main content

git-jira

PyPI Downloads

A git addon to manage Jira from git.

Prerequisites

Create a Jira API token: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/

Installation

The easiest (and best) way to install git-jira is through pip:

pip install git-jira

To make it work, you need a config.yml with your authentication credentials and default project.
Run git jira configure to generate this file.

The Jira server url should have the format https://yourservername.atlassian.net. For now, the authentication only supports API tokens.
The project id should have the format XX and is the one that you can find at the beginning of the issues (e.g. TP-123).
During the config you can also specify custom branch names. See Branch>Format section for more information.

Usage

Branch

Use git jira branch to create an issue in Jira and checkout to a branch with the format TP-1234-summary-of-issue.
The creation will ask the required fields interactively.
For now, the supported field types are:

  • Short text, paragraph
  • Number
  • Dropdown (single choice)
  • Checkbox (multiple choice)

You can also create a branch from an existing issue, using the issue code (TP-XX). For this, use git jira branch -k <issue_key>

Format

The default branch name format is issue_key-issue_summary replacing all non alphanumeric characters for -. You can override this by using the option -f or --format. This option will prompt a select menu that will show the formats you've specified while running configure. You can also select a custom format (using the last option).
For example, if you want the format to be feat/TP-123/summary-of-issue just pass feat/issue_key/issue_summary. The replacement for - in the summary can't be changed.

List

Use git jira list to list issues and their branches. By default, it list all issues in planned. You can use the flag -s or --status to show issues with other statuses.

Issue

Use git jira issue to check the info of an issue specified in a branch. If you're in a branch TP-10-issue-summary this command will show you the info related to the Jira issue TP-10.

Status

-s or --status: update the issue status.

Assignee

-a or --assignee: assign the issue to you or someone else.

Comment

-c <text> or --comment <text>: add a comment to the issue.

Caveats

git jira --help won't work. To see the global help, run git jira or git-jira --help

Development

virtualenv env 
source env/bin/activate
pip install -e ".[dev]"

Metadata

Release files for git-jira 0.5.0

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

Source distribution (sdist)

Source distribution for git-jira 0.5.0
File Size Uploaded Provenance Actions
git-jira-0.5.0.tar.gz 10.5 kB Without provenance Details for git-jira-0.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for git-jira 0.5.0
File Interpreter ABI Platform Actions
git_jira-0.5.0-py3-none-any.whl Python 3 none any Details for git_jira-0.5.0-py3-none-any.whl

Total release size: 22.2 kB

Release files / git-jira-0.5.0.tar.gz

Download URL git-jira-0.5.0.tar.gz
Size 10.5 kB
Tags Source
SHA-256 checksum
How to use checksums
05a32408052a667d04fbcb1f0da16ae80600ab94d47e3851dce87baab7222d9e
BLAKE2b-256 checksum
How to use checksums
12c72584d93df8fc8a90c66cf42b5f5d2b0ded0f84d13d843d438a765b1d7968
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.9.9

Release files / git_jira-0.5.0-py3-none-any.whl

Download URL git_jira-0.5.0-py3-none-any.whl
Size 11.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
585ac09d9666df77cb4b2c9cca306852c7cd95940080fc93c1644fb0d13e8f7a
BLAKE2b-256 checksum
How to use checksums
25c4ffe05d9fb6253de5d9f94691e02279434ddbee16ce3cb8ca37b4af743fd5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.9.9

Security for git-jira 0.5.0

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page