Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Page Contents
Table of Contents | ||
---|---|---|
|
Live Search spaceKey ZenGRCOnboardingGuide additional none placeholder Search our site type page
Overview
Info | ||
---|---|---|
| ||
For overall information on integrating Jira and ZenGRC, please see Jira Connector. |
After Jira and ZenGRC are connected, you can select the Jira option when setting up an audit. This documentation shows where that option resides, along with additional steps needed when setting up a Jira audit.
Tip | ||
---|---|---|
| ||
Existing audits cannot be converted to Jira. The option can only be selected during the creation of a new audit after the ZenGRC and Jira integration is complete. |
Step 1: Adding Basic Audit Information
To create a Jira audit, complete the following steps:
- Click New in the left-hand navigation and Audit.
Complete the fields and select Jira in the Managed in drop-down.
Tip title TIP The dropdown boxes that display when Managed in Jira is selected are determined by settings in the connected Jira instance. These selections do not impact ZenGRC. For example, if you select "Epic" in the Audit issue type dropdown, your audit is created as an Epic in Jira. And the selection of "Task" in the Request issue type dropdown means all audit requests imported during audit set up will be created as Tasks in Jira. But they still display in ZenGRC as requests.
In the Jira project dropdown, select a project. This displays additional Jira dropdowns. Make selections for each. These selections override settings chosen when establishing connection between your ZenGRC and Jira instances.
Continue making selections for the remaining Jira fields .
Warning title Beta Only Customersas determined by your Jira project.
- The following check boxes are available for those in the ZenGRC Beta programcheck boxes at page bottom provide the following functionality:
- Synchronize comments - Selection that provides read-only ability to see all Jira comments within ZenGRC without opening the Jira ticket.
- Synchronize attachments - Selection that displays Jira attachments as links within ZenGRC. The evidence still resides within Jira, but users don't need to open the Jira ticket, nor do they need Jira access.
Image Modified
Click Next. After this point, you can no longer change where the audit is managed
Info title NOTE For complete instructions on this step, please see Step 1: Adding Basic Audit Information.
Step 2: Defining the Scope
Step 2 in audit creation is the same for Jira and regular audits. For complete instructions on these steps, please see Step 2: Defining the Scope.
Step 3: Setting up Audit Requests - Jira
Note | ||
---|---|---|
| ||
Populating the requests template for a Jira audit has special considerations and is described in Configuring CSV Import for the Jira Connector. |
After configuring your CSV file for import, you can map them to controls. Please see Mapping Requests to Available Controls in Step 3: Setting up Audit Requests.
Steps 4 and 5
Step 4 and 5 in audit creation are the same for Jira and regular audits. For complete instructions on these steps, please see Step 4: Generating Assessments and Step 5: Reviewing and Starting the Audit.
Include Page | ||||
---|---|---|---|---|
|
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
VIDEO: ZenGRC Jira Demonstration |
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
TEMPLATE: Jira expanded template.csv |