JIRA-RPC
Python client for the JIRA SOAP API. Tested with JIRA 4.1 - 5.1 and Python 2.6 / 2.7.
Configuration
First, you need to set up the configuration. Either create a config.ini file in the jira folder, or if you’re using this in a Django project, you can put the settings in your settings.py, for example:
JIRA_RPC_USER = 'abc' JIRA_RPC_PASS = '123' JIRA_WSDL_URL = 'http://jira.example.com/rpc/soap/jirasoapservice-v2?wsdl' JIRA_TESTING = True JIRA_TEST_PROJECT = 'TEST'
WARNING If TESTING is set to True, the client connects to a project named TEST (which is assumed to exist on the server). This is useful for testing functionality on a test project before pushing into production (maintaining an entire JIRA server just for testing seems excessive). If you have a real project called TEST, you should change this by overriding the test project name in the settings (see config.example.ini).
Installation
The only requirement is Suds:
pip install -r requirements.txt
1 maintainer
Metadata
1 maintainer
Release files for jira-rpc 0.1
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-rpc-0.1.tar.gz | 6.5 kB | Without provenance | Details |
Release files / jira-rpc-0.1.tar.gz
| Download URL | jira-rpc-0.1.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7feae4d55ecff865008e853ca4a99146581978701296381a97f4fcec5adf5f15
|
|
BLAKE2b-256 checksum How to use checksums |
2d47c85470b9406aa078385c036f05bf2fdbe54ff4457c99a94851de5eddad6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for jira-rpc 0.1
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.
