Update JIRA tickets moved on a JimFlow Kanban board. See http://jimflow.jimdo.com.
This replaces the PHP cron job in JimFlowWall that is designed to run after JimFlowKlopfer. It uses the outputs of JimFlowKlopfer.
Usage:
$ jirathumper --url=<JIRA URL> --username=<username> --password=<password> --config=config.ini klopfer-output.json
The configuration file (e.g. config.ini) contains:
[columns] 0 = todo 1 = in-progress 2 = done
This maps column indexes (0 is the first one) to the titles of JIRA statuses.
The input file is produced by JimFlowKlopfer. It maps the current position (column index) of each item on the board, as identified by JIRA ticket ids.
jirathumper will then look up each ticket in JIRA and identify its current status. If this is diffent from the one indicated by the columns on the wall, it will look for possible transitions to take it into that state. If such a transition exists, it will be executed.
Metadata
Release files for jirathumper 1.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 |
|---|---|---|---|---|
| jirathumper-1.0.tar.gz | 3.4 kB | Without provenance | Details for jirathumper-1.0.tar.gz |
Release files / jirathumper-1.0.tar.gz
| Download URL | jirathumper-1.0.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
50b736396115bf4565c5093c4dba3303e9f6631af6cf153bbca495de0fbd1af7
|
|
BLAKE2b-256 checksum How to use checksums |
81301efe3ca28ee14340dbbd2171bbf7811c677c885cfd2a27cbbc181642c817
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for jirathumper 1.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.