Jira History
The Jira History library allows you to retrieve issues from JIRA in (almost) the same state as they were on the requested date/time.
In addition, a simple CLI is added to retrieve the status of a singular issue.
Installation
$ pip install jira-history-api
Example
from jira_history import Jira
from datetime import datetime
jira = Jira(url='https://jira-instance.com',
username='bob',
password='secret')
jira.get_issue(key='ISSUE-100',
datetime.strptime('12/11/2018 09:15:32', '%d/%m/%Y %H:%M:%S'))
Usage
Usage: jira-history [OPTIONS]
Options:
-u, --username TEXT Username that is able to query Jira [required]
-p, --password TEXT Password associated with the Username that is able to
query Jira [required]
-s, --server TEXT Jira server URL [required]
-k, --key TEXT Issue key to analyse [required]
-d, --date [%Y-%m-%d] Status of Jira issue key should reflect this date.
--verbose Increase verbosity for more logging
--help Show this message and exit.
Credits
The atlassian-python-api project, providing the Jira REST API calls used by this project.
Metadata
Release files for jira-history-api 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jira-history-api-0.4.0.tar.gz | 16.1 kB | Without provenance | Details for jira-history-api-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jira_history_api-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for jira_history_api-0.4.0-py3-none-any.whl |
Total release size: 29.0 kB
Release files / jira-history-api-0.4.0.tar.gz
| Download URL | jira-history-api-0.4.0.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a69acdb2ea95cea0eadaa5a57c428030fc8407c56fd2539770eb9fa2bb716d9
|
|
BLAKE2b-256 checksum How to use checksums |
3a49e8979eb99077735e5466b23ef0f7ed2056e182b30a0f85141c37b9c3e58a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.56.2 CPython/3.9.1
|
Release files / jira_history_api-0.4.0-py3-none-any.whl
| Download URL | jira_history_api-0.4.0-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e1fe0adc7f634b895e63ea6690ab342c8864dd92e8f06ee59296b2f7e2c3539
|
|
BLAKE2b-256 checksum How to use checksums |
7205e5ee44334d39509010e84bb2c5691065ae6a8756e91d28b9253495b06bb1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.56.2 CPython/3.9.1
|
Security for jira-history-api 0.4.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.