jira-ticket-migrate
This is a program to help migrate tickets between Jira servers. If you have the appropriate privileges, there are better ways of doing this! If you don't, all you have available are messy solutions (including this).
So what's this, then? This migrates tickets belonging to projects from one Jira server to Jira another server. If the project is fresh on the destination server, then ticket numbers will be preserved.
To see what's done, a set of before and after pictures tells the best story:
Source ticket
Migrated ticket
Notice that the following are preserved:
- title
- description
- priority
- status
- resolution
And possibly add the ticket number to that list (see above paragraph). Everything else is not preserved.
Note that this program assumes that you're migrating to a new-ish Jira (2018-ish), since there are some key differences between old and new Jiras.
Installation
Using pip,
pip install jira-ticket-migrate
Alternatively, you can run jira-ticket-migrate directly from source
using the script
run_jira_ticket_migrate.py.
Usage
Copy the example config file
config.yaml.example to config.yaml
cp config.yaml.example config.yaml
and fill it in.
Then run with
jira-ticket-migrate
You can specify a config file explicitly with the -c option:
jira-ticket-migrate -c /path/to/config.yaml
Otherwise it will look for it at the root of the repository.
Metadata
Release files for jira-ticket-migrate 0.1.4
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 | |
|---|---|---|---|---|
| jira-ticket-migrate-0.1.4.tar.gz | 5.8 kB | Without provenance | Details |
Release files / jira-ticket-migrate-0.1.4.tar.gz
| Download URL | jira-ticket-migrate-0.1.4.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e673befcb2f2e930dc2a006b89a402ec813c9ceb026c5d5173241c889df4a9dc
|
|
BLAKE2b-256 checksum How to use checksums |
fc5cb5604981c9ea7cda64484273c627b23b698e9930425ab66366901efd8a8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.21.0 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.7
|
Security for jira-ticket-migrate 0.1.4
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.