jira2vsts

Synchronize Jira issues to VSTS (Azure Devops)

Usage

Commands:

Usage: jira2vsts [OPTIONS]

  CLI for Jira2Vsts

Options:
  -v, --validate
  -l, --logfile FILE    Path to logfile  [required]
  -c, --config FILE     Path to the configuration file  [required]
  --loop-every INTEGER  Loop every X minutes
  -s, --send TEXT       Send one jira issue by code, format:
                        jira_issue_code,vsts_project_name
  --help                Show this message and exit.

Launch synchronization:

jira2vsts -c config.yml -l /var/log/jira2vsts.log

Check validy of the configuration file and for authentification information:

jira2vsts.py -c config.yml -l /var/log/jira2vsts.log --validate

Launch the synchronization every 60 minutes:

jira2vsts.py -c config.yml -l /var/log/jira2vsts.log --loop-every=60

Send one jira issue to VSTS:

jira2vsts.py -c config.yml -l /var/log/jira2vsts.log --send JIRA_ISSUE_CODE,VSTS_PROJECT_NAME

Installation

Simply run

pip install jira2vsts

Format of config file

Configuration file:

jira:
  password: {JIRA_PASSWORD}
  url: {JIRA_FULL_URL}
  username: {JIRA_USERNAME}
  add_hours: {JIRA_ADJUST_TIMEZONE_WHEN_SEARCHING}
  skip_large_attachments: {TRUE_OR_FALSE}
projects:
  {CODE_JIRA_PROJECT}:
    active: {TRUE_OR_FALSE}
    name: {NAME_OF_VSTS_PROJECT}
    type: {VSTS_DEFAULT_TYPE}
    states:
      - {LIST_VSTS_STATES_IN_ORDER}
    default_values:
        {VSTS_FIELD}: {VSTS_VALUE}
states:
  {JIRA_STATE}: {VSTS_STATE}
vsts:
  access_token: {VSTS_ACCESS_TOKEN}
  url: {VSTS_FULL_URL}

Todos

Manage comments

Metadata

Release files for jira2vsts 0.3.2

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

Source distribution (sdist)

Source distribution for jira2vsts 0.3.2
File	Size	Uploaded	Provenance
jira2vsts-0.3.2.tar.gz	7.0 kB	Jul 3, 2019	Without provenance	Details

Release files / jira2vsts-0.3.2.tar.gz

Download URL	jira2vsts-0.3.2.tar.gz
Size	7.0 kB
Tags	Source
SHA-256 checksum How to use checksums	`10a2c368907a5ae39fdb0d4fa3569f9340e7d543923cdfc2717d37bffe91f95d`
BLAKE2b-256 checksum How to use checksums	`64deed6e5a3eab2ebd4330147c7e66e05603a8dfe1213e7fdbaa9ba0d8d7eb44`
Upload date	Jul 3, 2019
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/39.1.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.1`

Security for jira2vsts 0.3.2

Report project as malware

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.