Synchronizing PSA Project Tasks to Jira Issues

Note:

The synchronization between project tasks and issues is not bi-directional. Depending on your configuration, either PSA or Jira are used as the source of truth. Any changes that you make in the target application will not be automatically synced to the source application. The only exception is the Status field if PSA is your source application, see Updating the Status of Project Tasks Based on the Status of Related Issues.

This section is about the Sync Project Tasks from PSA to Issues in Jira workflow. For information on the opposite direction, see Synchronizing Jira Issues to PSA Project Tasks.

If you enabled the Sync Project Tasks from PSA to Issues in Jira workflow via the Feature Console, eligible project tasks are automatically synchronized to Jira. A project task is eligible for syncing if all of the following are true:

• The Jira Issue Type Category and Jira Issue Type fields are populated.
• The related project is linked to a Jira project or Jira issue.
• If the project task is a child task, its parent task must be linked to a Jira issue.
• The Sync with Jira checkbox is selected.

When you create a project task in PSA, the connector creates a new Jira issue with the information listed below. Similarly, when you edit an eligible project task in PSA, the connector updates the related issue in Jira.

Key: * – Mandatory field

PSA Project Task - Jira Issue Default Mapping

PSA Project Field	Jira Issue Field
Project Task Name *	Summary
Estimated Hours	Original Estimate
Long Description	Description
Priority	Priority
Status	Status

When the issue is created in Jira, the Jira Correlation ID of the project task is automatically populated with the issue key.

The issue is created in Jira with the default status defined for that issue type and project, through the associated issue workflow. This is standard Jira functionality. If the status you set for the project task isn't converted to the default status in Jira, after creating the issue, the connector immediately tries to update the status. If the new status is a valid transition for that issue workflow, the status is updated accordingly. If the transition is not valid, the status is not updated and the connector sends an error message. For more information on issue workflows in Jira, see the Atlassian documentation.

Notes:

• The Priority and Status values defined for the project task in PSA are not directly copied to the Jira issue. This is because Jira and PSA have different values for the Priority and Status fields. You can configure how PSA priorities and statuses are converted to Jira priorities and statuses for each project. For more information, see Customizing the Priority and Status Value Mappings.
• If you don't define a priority for a project task in PSA, the Jira issue is created with the default priority. Note that if you are using Jira Server, the default priority might vary between different projects, depending on the priority schemes defined. For more information about priorities and priority schemes, see the Atlassian documentation.
• The reporter of the issue is always set to the user who authenticated the Jira application via the Feature Console.
• After an issue is created in Jira, you cannot update the related project task's Jira Issue Type Category and Jira Issue Type fields in PSA. If you want to change the issue type in Jira, you must delete the project task in PSA, create a new project task with the correct type, and sync it with Jira.

If you create a project task hierarchy in PSA, it is reflected in Jira. Because PSA and Jira establish hierarchy in different ways, the following limitations apply:

• You must first sync the parent level project tasks before you can sync its children project tasks.
• Standard issue types, such as stories and tasks, are linked to epics using the Epic Link field in Jira. In all other cases, the hierarchy is established through the Parent Link Field mapping. To configure this mapping, see Example 3 - Map Project Task Parent Link Field, Epic Link, and Epic Name Fields.
• Sub-task issue types can be created for all standard issue types, except for epics.
• Sub-task issue types cannot be used for parent projects tasks.
• If you are mapping projects to issues, a top-level project task can be a sub-task issue type. If you are mapping projects to projects, only standard issue types can be top-level project tasks.

When you delete a project task in PSA, the related issue is automatically deleted from Jira. If the project task has child tasks that are linked to sub-task type issues in Jira, the child tasks are deleted from PSA and the sub-task issues are deleted from Jira.

Note:

Issues are not deleted from Jira if you deselect the Sync with Jira field or remove the value of the Jira Correlation ID field on the related project task in PSA before deleting it.

If an error occurs during the synchronization, the PSA user who created, updated, or deleted the project task receives an email notification and a Foundations error message is created. In addition, in specific cases, an app log record is created for each project task that failed to sync with Jira. For more information, see Viewing Project Task to Issue Synchronization Errors.