Jira

The P4 Code Review integration with Atlassian Jira allows code reviews and committed changes to be associated with Jira issues. This makes it easy to reference associated issues, and see the state of a code review or committed change within Jira.

To associate a code review with a Jira issue, include a Jira issue identifier in the review's description, such as SW-123. P4 Code Review links to the Jira issue and creates a link within the Jira issue to the code review in P4 Code Review.

For example, if Jira issue SW-123 is found in the text, a hyperlink appears:

Multiple Jira issues can be included in the changelist description. As a code review progresses, P4 Code Review updates each associated Jira issue with the review's current status.

For instructions on how to configure basic Jira integration, see Basic Jira integration.

Additionally, if you have the P4 Defect Tracking Gateway (P4 DTG) configured to integrate P4 Server jobs with Jira issues, P4 Code Review can be configured to add a link to a job within a Jira issue. A P4 Server job is a numbered (or named) work request managed by P4 Server. For an introduction to this built-in feature of the P4 Server, see the Jobs section in the P4 CLI Reference

For a comprehensive guide to the P4 Defect Tracking Gateway, see the P4 Defect Tracking Gateway Documentation.

Job links are created when a new Jira work item or a job is created or updated. This gives you direct access to the job from a link in the Issue Links section of the Jira issue.

For instructions on how to configure Jira integration and P4 Server job links, see Jira integration with jobs.