Mapping P4 Plan columns and Jira fields

This topic explains how to integrate P4 Plan with Jira Server. Atlassian is deprecating Jira Server, which means that the Jira Server integration will reach end-of-life soon. If you use Jira Cloud or Data Center, see the Jira integration documentation.

Jira fields added to P4 Plan columns by the integration are appended with (Jira) to distinguish them from other columns. P4 Plan columns added to Jira are appended with [P4 Plan]. Project-specific P4 Plan columns added to Jira also include the project name. For example, Database ID [P4 Plan, Support Project].

The Jira URL, Project - Issue Type, and Resolution fields are always synced between P4 Plan and Jira. To sync additional fields from Jira to P4 Plan, make changes in the Jira field synchronization category in the Project Integration Settings dialog box.

The following information explains how P4 Plan and Jira fields are mapped when using the integration.

Numeric columns/fields

All numeric P4 Plan columns will generate two additional fields in Jira: Summary and Stat. For example: Estimated Ideal Days [P4 Plan Stat]. Do not update or delete these fields.

URL columns/fields

URL columns/fields are available in both Jira and P4 Plan to make it easy to go to items in each application.

  • In P4 Plan, the column is Jira URL (section name).
  • In Jira, the field is P4 Plan URL [P4 Plan, Project name].
The P4 Plan server hostname must be set in Admin area in P4 Plan so URLs are generated correctly.

Attachment columns/fields

When the integration is enabled, an Attachments (Jira, <P4 Plan section>) column is available in P4 Plan, which contains links to attachments in Jira for a synced item. You can download all attachments for a synced item from Jira to store in P4 Plan. See Migrating attachments.

Other columns

The following default P4 Plan columns and Jira fields are mapped between the applications.

P4 Plan column Jira field Notes
Item name Summary

 

Comments Comment

 

Assigned to Assignee P4 Plan supports multiple assignees, but Jira does not. In Jira, the Assigned to [P4 Plan] column is displayed. It contains a list of all assigned users from P4 Plan. The first user in the list is set as the Assignee in Jira. To assign an item in Jira, use the Assign to functionality. Jira updates the assigned user in the Assignee field and adds one user to the Assigned to [P4 Plan] list. If you want to assign multiple users from Jira, you must use the Assigned to [P4 Plan] field for assignments.
Originally created by Reporter

 

User story / Detailed description Description

 

Work remaining Logged Work, Estimated, Remaining Estimating works differently in P4 Plan and Jira. In P4 Plan, Estimated ideal days or Points are used in the Product Backlog to estimate user stories. These are then committed to sprints where teams break them down and given estimates as a Work remaining value. If the Estimated value is not set in Jira and an item with a Work remaining value is synced from P4 Plan, both the Jira Estimated and Remaining values are set to the P4 Plan Work remaining value. Future updates to the Work remaining value in P4 Plan will not change the Estimated value, but will update the Remaining value. Logged work does not have a corresponding column in P4 Plan and is not synced.
Finish Due (date) For P4 Plan Task Schedule items. The fields are not populated for QA and Product Backlog items that do not have finish dates. If these items are committed to a sprint, the Jira Due value is set to the P4 Plan Finish value for the sprint they are committed to.

Adding write access for Jira custom fields

The integration supports adding write access for custom Jira fields in P4 Plan. To do this, edit the integration settings file.