The 3rd party Jira package, including the python Jira API, will be useful for automatically creating/updating Jira DRP (or other production tickets) from within the operations production environment. For instance, this allows a data production campaign to be defined ahead of execting the campaign, and allows the status of the steps of the campaign to be updated as part of the 'bps submit' process.
For DP0.2, the operators, specially installed Jira on their submit machine node to gain access to the functionality (available as part of the prodstat module).
While the ops-campaign-tooling is currently in flux, and will change, it is likely that at some level it will be convienent to update Jira tickets automatically as part of campaign execution, so it will be useful to have Jira as a product that can be 'setup' along with the operations stack.
We also note that currently Jira requires a passwd login, which is handled with a .netrc file for each operator. Eventually this will transition to a token or other authentication mechanism, at which time the version of the Jira interface will need to be updated.