To support the complex differences between field values in PSA and Jira, the integration transforms the values from one application before syncing them with the other. This is done according to the mappings defined in a Foundations Data Transformation Table. For more information, see Creating a Data Transformation Table.
Priority Value Mappings
The Priority picklist on the Project, 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 field.
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 administrators to overwrite the default values and add new ones. In addition, Jira Server supports creating priority schemes, a feature that enables administrators to define a different set of Priority values for each Jira project.
In Jira, the Priority is required. When creating an issue, if a priority is not defined, the default priority is used.
Status Value Mappings
The integration comes with a predefined set of mappings. You can now directly copy PSA fields from the Status picklist on the Project, Project Task object in PSA to the Jira Status field in Jira and vice-versa using the respective mappings.
When creating an issue, if a status is not defined, the default status is used. Issues are always created in Jira, with the initial status defined for the associated feature.
Time Entry Status Mappings
If you are synchronizing your PSA Project to a Jira Issue, you can configure the integration to set certain field values on the PSA project when you set the Jira issue to a status belonging to a particular Jira issue status category. Jira provides three categories of issue status. For example, To Do, In Progress, and Done. In Jira, you map each status to one of the categories.
For more information on priorities and statuses, see the Atlassian documentation.
Predefined Default Mappings
The integration 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 mappings.
PSA to Jira Priority Value Mappings
The PSA to Jira Priority Value mapping table is used to translate the PSA Project Task priority value to the correct Jira issue priority when you create a PSA Project Task.
| PSA Value |
Jira Value |
|---|---|
| P1 | Highest |
| P2 | High |
| P3 | Medium |
| P4 | Low |
| P5 | Lowest |
Jira to PSA Priority Value Mapping
The Jira to PSA Priority Value mapping table is used to translate the Jira issue priority value to the correct PSA Project Task priority when you create a Jira issue.
| Jira Value |
PSA Value |
|---|---|
| Highest | P1 |
| High | P2 |
| Medium | P3 |
| Low | P4 |
| Lowest | P5 |
Jira to PSA Status Mapping
The Jira to PSA Status Mapping table is used in PSA Project to Jira Issue mode to map Jira Issue Status to PSA Project Stage.
| Jira Value |
PSA Value |
|---|---|
| Done | Completed |
| In Progress | In Progress |
| To Do | Planned |
Jira to PSA Time Entry Status Mapping
The Jira to PSA Time Entry Status Mapping table is used in PSA Project to Jira Issue mode to map Issue status category to either true or false for the Closed for Time Entry checkbox. For each status category marked as true in the table, the Closed for Time Entry checkbox will be checked.
| Jira Value |
PSA Value |
|---|---|
| Done | true |
| In Progress | false |
| To Do | false |
Jira Issue Types to Issue Type Category Mapping
The Jira Issue Types to Issue Type Category Mapping table is used when you create an issue in Jira, to set the correct Issue type category on the PSA Project Task. Each issue type you use in Jira needs an entry in this table.
| Jira Value |
PSA Value |
|---|---|
| Bug | Standard Issue Type |
| Epic | Standard Issue Type |
| Story | Standard Issue Type |
| Sub-task | Sub-task Issue Type |
| Task | Standard Issue Type |