Jira Set-Up

The following are the instructions on setting up the Jira in order to satisfy minimal requirements from the point of view of the Identity Manager Certificate Signing Request (CSR)/Certificate Revocation Request (CRR) approval workflow. This will enable a user to integrate such Jira deployment with the CENM CSR/CRR approval workflow plugin.

Create a user with an administrative permissions and make sure it is assigned to the default groups: jira-administrators and jira-software-users. The following shows an example for a Test user setup.

jira 7

Create two projects (one for Certificate Signing Requests and one for Certificate Revocation Requests) of the type of Process Management. The following shows final settings for both projects.

jira 6

Make sure that both projects (CSR and CRR) have the following workflow configured.

jira 1 Tickets are moved from Approved status to Done automatically, once the request is signed by the HSM.

Additionally, the following 3 custom fields need to be created and configured in Jira:

  • Request ID
  • Reject Reason
  • Reject Reason Description

The following snippets depict the configuration for those fields:

jira 4 jira 3 jira 2 jira 5

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.