Synchronizing Jira Issues to PSA Project Tasks

Note:

The synchronization between issues and project tasks 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. This section is about the Sync Issues from Jira to Project Tasks in PSA workflow. For information on the opposite direction, see Synchronizing PSA Project Tasks to Jira Issues.

If you enabled the Sync Issues from Jira to Project Tasks in PSA workflow via the Integration Hub Connector: Jira - PSA feature, eligible Jira issues are automatically synchronized to PSA project tasks. For a Jira issue to be eligible for syncing to PSA, the following must be true:

• The Jira issue must be of a predefined issue type.
• The Jira issue must be created for a Jira project that is correlated to a PSA project. If you are mapping PSA projects to Jira issues, the issue must be a child issue of the correlated issue. For more information, see Synchronizing PSA Projects to Jira Issues.

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

Jira Issue - PSA Project Task Default Mapping

Jira Issue Field	PSA Project Task Field
Description	Long Description
Key	Jira Correlation ID
Original Estimate	Estimated Hours
Priority	Priority
Status	Status
Summary	Description
Summary	Project Task Name
Type	Jira Issue Type
Type of Issue Type (not visible in the Jira UI)	Jira Issue Type Category

In PSA, the project task is linked to the relevant project.

• If you are mapping PSA projects to Jira projects, the project task is linked to the PSA project correlated to the Jira project the issue was created in.
• If you are mapping PSA projects to Jira issues, the project task is linked to the PSA project correlated to the parent Jira issue of a predefined type. For example, you can link a PSA project to an epic in Jira and define that issues of the type Story are eligible for syncing to PSA as project tasks. When you create a story for the epic, a project task is created in PSA and linked to the PSA project that is correlated to the epic.

Notes:

• The Priority and Status values defined for the issue in Jira are not directly copied to the project task in PSA. This is because Jira and PSA have different values for the Priority and Status fields. You can configure how Jira priorities and statuses are converted to PSA priorities and statuses for each project. For more information, see Customizing the Priority and Status Value Mappings.
• If the Summary field in Jira exceeds 80 characters, it is truncated in the Project Task Name. The full summary is retained in the project task's Description.
• If the Description field in Jira contains formatted text, it is stored in Markdown format in Jira. When this is synced with PSA, the Markdown syntax is retained. As a result, you might see plain text with Markdown syntax characters in PSA.
• Files attached to the Jira issue are not synced to PSA.
• Issue hierarchy from Jira is not recreated in PSA. All project tasks are created at the same level, without child tasks.
• By default, when an issue is synced to PSA, the project task's Start Date & Time and End Date & Time fields are blank. This is because Jira doesn't provide standard fields for those values. If you want these fields to be populated in PSA, you must create custom date time picker fields in Jira and modify the mappings. For more information, see Example 4 - Map Project Task Start Date & Time and End Date & Time.

When you delete an issue from Jira that was already synced to a PSA project task, the project task is automatically deleted. This only applies if the project task can be deleted from PSA.

If an error occurs when syncing issues to project tasks, an email notification is sent to the PSA resource linked to the Jira user who created the issue. If the Email field for the resource is blank in PSA, the notification is sent to the user specified in the Integration Hub Connector: Jira - PSA custom setting.

When an error occurs, a Foundations message is also created with the publisher name PSA/IHCIntegration.Jira. For more information, see Viewing Integration Hub Connector: Jira - PSA Error Messages.