Customizing the Priority and Status Value Mappings

Note:

This only applies if you intend to sync PSA project tasks with Jira issues or vice-versa. If you are not interested in the synchronization between project tasks and issues, ignore this section.

The Priority and Status picklists on the Project Task object in PSA cannot be copied directly to or from the respective fields in Jira. This is because Jira and PSA have different values for the Priority and Status fields.

By default, the Priority field in Jira contains descriptive values (Highest to Lowest), while the Priority picklist in PSA uses a P1 to P5 value system. Both applications enable admins to overwrite the default values and add new ones. In addition, Jira Server supports creating priority schemes, a feature that enables admins to define a different set of Priority values for each Jira project.

The Status field in PSA is a customizable (unrestricted) picklist. Statuses in Jira are configured through workflows. A Jira issue workflow contains a set of statuses and the allowed transitions between them. This means that a Jira user might not be allowed to move an issue currently in "Draft" status to "Done", depending on how the associated issue workflow is configured. By default, PSA allows users to change the status of a project task without any restrictions.

In Jira, both the Priority and the Status fields are required. When creating an issue, if a priority is not defined, the default priority is used. Issues are always created in Jira with the initial status defined for the associated workflow.

For more information on priorities and statuses, see the Atlassian documentation.

To support the complex differences between the Priority and Status fields in PSA and Jira, the connector transforms the values from one application before syncing them with the other. This is done according to the mappings defined in a Foundations configuration item record.

For both priority and status, you can define a default mapping and as many project-specific mappings as you need. For example, most of your Jira projects correlated to PSA projects might use the same issue workflow. You might also have one or two Jira projects that use a different workflow. In that case, you can use the more common workflow to map the default status values and create separate mappings for the other projects. Similarly, if you are using Jira Server, you might have multiple priority schemes defined. You can use the most common scheme for the default priority mappings and create additional project-specific mappings for the other schemes.

Predefined Default Mappings

The connector comes with a predefined set of mappings. We recommend that you customize the predefined mappings to avoid errors when syncing from one system to the other.

Here is a list of predefined priority and status mappings.
Note:

The Sync Project Tasks from PSA to Issues in Jira workflow uses both status value mappings from PSA to Jira and from Jira to PSA. This is to support updating the status of project tasks after the related issue is moved to a new status.

Default PSA to Jira Status Value Mappings

PSA Value

Jira Value
Draft To Do
Planned To Do
Started In Progress
Blocked In Progress
Complete Done
Deferred Done

Default Jira to PSA Status Value Mappings

Jira Value

PSA Value
Open Draft
To Do Planned
In Progress Started
Under Review Blocked
Done Complete
Cancelled Deferred
Default PSA to Jira Priority Value Mappings

PSA Value

Jira Value
P1 Highest
P2 High
P3 Medium
P4 Low
P5 Lowest

Default Jira to PSA Status Value Mappings

Jira Value

PSA Value
Open Draft
To Do Planned
In Progress Started
Under Review Blocked
Done Complete
Cancelled Deferred
Default Jira to PSA Priority Value Mappings

Jira Value

PSA Value
Highest P1
High P2
Medium P3
Low P4
Lowest P5

Creating a New Foundations Configuration Item for Priority and Status Mappings

The predefined mappings are configured in a managed Foundations configuration item named IHC Jira-PSA Priority & Status Mappings. You can clone the existing record and then modify the mappings.

Note:

The managed record contains the mappings for both the Sync Project Tasks from PSA to Issues in Jira and Sync Issues from Jira to Project Tasks in PSA workflow in the Large Data field. Depending on the workflow you plan on enabling, you must modify the appropriate sections. You can delete the sections for the other workflow as they are not used.

To customize the mappings:

  1. From Setup, click Custom Code | Custom Metadata Types.
  2. Next to Foundations Configuration Items, click Manage Records. A list of existing configuration items displays.
  3. Click IHC Jira-PSA Priority & Status Mappings. The predefined record displays.
  4. Click Clone. A new record is created.
  5. [Optional] Change the label of the record.
  6. Change the Foundation Configuration Item Name. This must be unique. For example, append 2 at the end of the existing name, IHC_Jira_PSA_Priority_Status_Mappings2.
  7. Leave Process as psa:ihc:jira and Identifier as project-task:mappings.
  8. Increment the Small Data value by one. For example, enter 2. This is the version of the mappings record. 
    Note:

    Only the record with the highest Small Data value is used by the connector.

  9. Leave the Object and Field values as "None".
  10. Change the mappings defined in the Large Data field.
    The Large Data field contains a JSON structure that defines the mappings. For more information on how to customize the JSON, see Large Data JSON Attributes and Large Data JSON Examples.
  11. Leave Enabled as selected.
  12. Click Save. The record is now saved and will be used after you activate the Sync Project Tasks from PSA to Issues in Jira or the Sync Issues from Jira to Project Tasks in PSA workflow using the Feature Console.
Note:

If you change the mappings after activating the connector, you must disable the Sync Project Tasks from PSA to Issues in Jira or the Sync Issues from Jira to Project Tasks in PSA workflow using Feature Console and enable it again to apply the changes.