Copy/update JIRA issues to match your VersionOne stories.
This is a little utility you can use for creating/updating JIRA issues matching one’s VersionOne stories.
pip install --allow-external elementtree --allow-unverified elementtree versionone-to-jira-reflector
If you’re wondering what the --allow-external elementtree and --allow-unverified elementree lines are about: This program relies upon the Python SDK released by the VersionOne team (albeit, an unofficial distribution of it), and that SDK relies upon elementree which is unavailable through verified/local PyPI sources.
The first time you run the command, it will ask you for various bits of information that it will use for interacting with VersionOne and JIRA.
The app will proceed to ask you for connection information if such details have not previously been saved, and will create or update a JIRA issue to match your V1 story with the story identifiers you have supplied.
All configuration data except passwords will be written to ~/.versionone-to-jira-reflector should you need to edit it after saving. Passwords will be queried from (and saved to) the system keyring.
Note that you can run this command for multiple stories simultaneously, too:
v1tojira D-01084 B-08244 B-08084
And that you can prevent a web-browser tab from being opened for each created or updated ticket:
v1tojira --no-open D-01084 B-08244 B-08084
See v1tojira --help for more information.
Although this is a totally workable solution, this was mostly a quick hack to solve a temporary need, and it isn’t exactly code that I’m proud of. If you end up using this tool, feel free to fork this code and clean things up to your liking.
Release history Release notifications
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size & hash SHA256 hash help||File type||Python version||Upload date|
|versionone-to-jira-reflector-0.5.9.tar.gz (8.3 kB) Copy SHA256 hash SHA256||Source||None||Apr 5, 2016|