Jira
Last updated
Was this helpful?
Last updated
Was this helpful?
PlexTrac offers a robust integration with Jira Cloud and Jira Data Center, enabling seamless collaboration between red and blue teams without the need to switch tools. This integration can be configured either for the entire tenancy or customized for specific clients.
The PlexTrac-Jira integration supports various synchronization options:
Unidirectional from PlexTrac to Jira
Unidirectional from Jira to PlexTrac
Bidirectional
One-time from PlexTrac to Jira
One-time from Jira to PlexTrac
Two primary implementation scenarios exist:
Tenancy-wide integration: A single Jira connection is supported across the entire PlexTrac instance.
Client-specific integration: Each client can have its own dedicated Jira instance integration.
In cases where a user, based on associated permissions, has access to both the tenancy-wide and a client-specific integration, they will be prompted to choose the appropriate Jira instance when linking a finding to a Jira ticket. This flexibility allows organizations to tailor the integration to their specific workflow needs.
Step 1: Click Integrations under "Tools & webhooks" from the Admin Dashboard.
Step 2: Click the Jira box.
Step 3: Click New connection.
Step 4: Enter a connection name in the provided box. Identify if this connection is across all clients or is client-specific.
Step 5: Click Continue at the bottom of the page.
Step 6: On the second tab, input the correct information in the provided fields. The application provides instructions on the right on how to find information for each field.
If "Every day" is selected for the refresh frequency, the daily synch time will occur at 04:45 UTC (9:45 PM MTN).
Step 7: Click Save & continue at the bottom of the page.
If the connection is unsuccessful, an error message will be provided at the top of the page.
If a successful connection is made, the tool will progress to the next tab to continue.
Step 8: On the Select projects tab, choose the project(s) from Jira to integrate with by clicking the box next to the desired project. Only these projects will be available when creating tickets from findings. Click Continue with x projects when finished.
It may take some time to set up the connections, depending on the number of projects selected.
Step 9: On the Map fields & save tab, select a project to configure from the pulldown "Project name."
Step 10: Select the Jira project issue type from the provided list to configure.
Step 11: Review the default mappings and adjust as desired.
PlexTrac findings cannot be created from Jira issues. Syncing from Jira to PlexTrac will occur after the initial issue creation.
The symbol displayed between the PlexTrac and Jira fields identifies the direction and synch of information between fields.
Required fields are identified with a red asterisk and cannot be deleted.
To modify the direction, click the icon and select the desired direction from the options provided. The icon arrow points to the direction information flows between the two fields.
Jira to PlexTrac (Continuous sync)
When a change occurs in a Jira issue, the connected PlexTrac finding will be updated. When changes occur in PlexTrac, the Jira issue will not be updated. PlexTrac findings cannot be created from Jira issues. Syncing from Jira to PlexTrac will happen after the initial issue creation.
Bidirectional (Continuous sync)
When a change occurs in a PlexTrac finding, the connected Jira issue will be updated. When changes occur in Jira, the PlexTrac finding will be updated.
PlexTrac to Jira (Continuous sync)
When a change occurs in a PlexTrac finding, the connected Jira issue will be updated. When changes occur in Jira, the PlexTrac finding will not be updated.
PlexTrac to Jira (One-time sync) Syncs data from PlexTrac to Jira upon ticket creation. A change in a PlexTrac finding will not be synced to the connected Jira issue.
If a bidirectional or Jira to PlexTrac direction is configured, be aware that a user in Jira could change findings values in PlexTrac despite not having access or permissions to do so within PlexTrac.
Step 12: Repeat this process for each project issue type.
The options available in the PlexTrac field pulldown menus are contextual to the values selected in the Jira column. To change the options provided for PlexTrac fields, change the field provided in the Jira column.
To add a new row for additional mappings not provided by default, click the plus icon at the bottom (after the last mapping).
Not all fields in PlexTrac can be mapped to all fields in Jira. In those scenarios, fields will display a red icon when hovered over and a text description of "incompatible data type" when scrolling through the list of fields.
Click the pulldown menu in the PlexTrac field to select the desired field. Then click the pulldown menu in the Jira field to associate the desired mapping. Finally, select the desired flow.
To delete any row, hover over it with the cursor and click the red trashcan icon.
Step 13: Click Save & Continue.
PlexTrac custom fields can be added for mapping to a Jira field, including fields with a dropdown menu.
Step 1: Click the plus icon at the bottom of the Map fields tab (after the last existing mapping).
Step 2: Click the pulldown menu in the Jira column of the newly added row to view the available fields in Jira to map.
The Jira field must have a data type value of "String," "Option of strings," or "Non-Nullable String." The Jira data type is shown in the right column of the Jira fields when the options provided in the Jira field pulldown menu are viewed.
Step 3: Click within the PlexTrac column pulldown menu of the row just added and select "Custom Field" from the list.
Step 4: Enter the custom field key name.
If the custom field key entered is different than what exists in PlexTrac, the mapping will not work, and a new custom field with that incorrectly entered value will be created in PlexTrac.
Step 5: Click Save.
Jira custom fields available for mapping can be viewed by clicking a field in the Jira column and scrolling to the bottom of the window under the label "CUSTOM."
Jira custom fields from a third-party plugin cannot be mapped.
The finding reported date can be mapped so that any future findings will automatically update this value in Jira.
Step 1: Click the plus icon at the bottom of the Map fields tab (after the last existing mapping).
Step 2: Click the pulldown menu on the Jira column of the row just added and select "Start Date."
Step 3: Click the pulldown menu on the PlexTrac column of the same row and select "Created Date."
Step 4: Click Save.
Any linked findings in PlexTrac will now be updated in Jira. If the mapping is configured for bidirectional, changes in this value in Jira will update in PlexTrac the next time data synchronization occurs.
Step 1: From the Admin Dashboard, click Integrations under "Integrations & webhooks."
Step 2: Click the Jira box that shows the status of "Connected."
Step 3: Click Edit under the "Actions" menu of the connection to modify.
This screen is also the location to disable or delete a Jira connection.
Step 4: Go to the desired tab to adjust as desired.
Connection availability and selected clients cannot be edited. To change availability or clients, create a new connection.
Two ways exist to disable a Jira integration:
Temporarily, by toggling the button under the "Enabled" column.
2. Permanently, by clicking Delete under the three dots in the "Actions" column.
A data type value of "any" is displayed when PlexTrac does not know the data type due to how the field was added to Jira through a plug-in. Mappings with a data type value of "any" may not work as intended.
The custom field key is located on the Custom Fields tab of a finding that is found via the Reports module.
