Synchronizing Jira Issues to PSA Project Tasks

If you enabled the Sync Jira Issues to PSA Project Tasks field, 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.
  • The Salesforce user Automated Process must have a permission control that allows it to create Timecard Headers under and synced PSA Project.

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 work logs are also automatically resynced with PSA task time records by clicking Synchronizing worklogs from Jira. For more information, see Project Task Fields.

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 using the data transformation table Jira to PSA Status Mapping. For more information, see Customizing the 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.

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 on the PSA Direct for Jira Settings tab.

When an error occurs, a Foundations message is also created with the publisher name PSA Direct for Jira/Error. For more information, see Viewing PSA Direct for Jira Error Messages .

Updating PSA Projects Based on Jira Issue Status

If you enabled the Update PSA Project based on Jira Issue field on the PSA Direct for Jira Settings tab, PSA projects are automatically updated based on the status of the linked Jira issue. When a Jira issue is moved to a status that belongs to a specific category, a specified PSA project field is automatically updated with a specified value.

Each status in Jira has one of the following categories: "To Do", "In Progress", or "Done".

By default, when an issue is moved to any status with the category of "Done", the related project is set to Completed in PSA, and the Closed for Time Entry checkbox on the PSA project is ticked.

Depending on your requirements, this feature can have different results. Some examples include:

  • If a custom issue type called Phase is moved to "Completed", the Stage field in PSA is set to "Completed".
  • If a custom issue type called PSA Project is moved to "Closed", the Project Status field in PSA is set to "Green".

For more information on how to configure this feature, see Configuring the PSA Direct for Jira Settings.

Mapping Jira ArrayAll Fields to PSA Fields

If you have enabled the Sync Jira Issues to PSA Project Tasks field, then any relevant Jira issues will be automatically synchronized with PSA project tasks.

For a Jira issue to be eligible for syncing with PSA, the following must be true:

  • The Jira issue must be of a specific, predefined issue type.
  • The Jira issue must be created for a Jira project linked to a PSA project. If you are mapping PSA projects to Jira issues, the issue must be a child issue of the corresponding Jira issue.
  • If you create a Jira Issue with the Jira Issue Type as "Epic," you can map the Jira field with multiple values synced from the array list to the PSA project.

To map a Jira ArrayAll field to a PSA Project or Project Task field:

  1. To support different Jira custom fields, you must create custom metadata records. For more information, see Example 3 - For Array Types Custom Field.
  2. Navigate to the PSA Direct for Jira Mappings Lightning page.
  3. Create a new mapping in the Jira Issue to PSA Project Mappings or Jira Issue to PSA Project Task Mappings components.
  4. In the Source Field Path, select the multi-select picklist you created in step 1.

    For example:

    • In the Source Type field, select the value as "field".
    • In the Source Field Path, select multiple values from the multi-select picklist. For example, fields > customfield_10400 > value.
    • In the Target field, select the value as "Expense Notes".
  5. Click Save.
  6. Select multiple values from the Custom MultiSelect List in the Jira Issue Task and click Save.
  7. Refresh the PSA Project or PSA Project Task, which is mapped to the Jira Issue Task, and you will view the multi-select values under the Expense Notes field.