Configuring the PSA Direct for Jira Settings

The PSA Direct for Jira connector setup is done via the PSA Direct for Jira Settings tab. Depending on your requirements, you might not need to perform all the steps. For a complete description of the available fields, see PSA Direct for Jira Settings Fields.

Note: To use the PSA Direct for Jira Settings tab, you must be assigned the PSA Direct for Jira - Configure Jira permission set.

[Optional] Enter the email address that will receive error notifications if the relevant resource does not have an email address, for example, if the connector fails to synchronize a task.

[Optional] Select the Use Parent Link checkbox to use the Parent Link custom field provided by Jira to build a hierarchy from any issue type to issue type. By default, it is deselected.

  1. [Optional] Select the Sync PSA Projects to Jira checkbox to check whether Sync to Jira is skipped on PSA projects. The Jira projects are synced to PSA projects if the Sync to Jira field is selected in PSA projects.
    1. Depending on the requirement, select Jira Projects or Jira Issues checkboxes to map PSA Projects.
    2. If you have selected the Jira Issues checkbox to synchronize to Jira Issues, then, in the Jira Issue Type field, enter the name of the issue type. For example, Epic.
  2. [Optional] Select the Update PSA Project based on Jira Issue checkbox to ensure that the eligible PSA projects are updated based on Jira Issue. By default, it is deselected.
    Note: Note: If the connector is enabled, and you have a saved value in the PSA Direct for Jira custom setting for the Jira Projects checkbox in the Project Settings component, and you change your selection, then updates will stop for all synchronized projects.
  1. Select the Sync PSA Project Tasks to Jira Issues checkbox to ensure that the eligible PSA project tasks are synced to Jira issues. If you have selected the Sync PSA Project Tasks to Jira Issues checkbox, you can choose to update the PSA project depending on the status of the Jira issue. For example, you can close the PSA project to time entry when you set the Jira Issue to Closed.
  2. Select the Update Projects based on Jira Issue checkbox to ensure that the eligible PSA projects are updated based on Jira issue status.
  3. Review the data transformation table Jira to PSA Time Entry Status Mapping. This determines the category of the Jira issue statuses used for updating PSA projects. You can choose To Do, In Progress, or Done. The default is Done set to True.
  4. Review the default mapping supplied in the Jira Issue to PSA Project mapping. They are set to update the PSA project stage and the Closed For Time Entry. You can override these mappings.

Select the value from the Timecard Status field to determine the status in which the connector creates timecards. The values available are the active values in the picklist on the Timecard object.

Note: The Timecard Settings only display active picklist values. If the default is not active, it does not display a default. Once you have saved the timecard status, the setting is not updated if you deactivate or delete the value from the picklist on the Timecard object.
  1. [Optional] Select the Sync Jira Issues to PSA Project Tasks checkbox to ensure that the eligible Jira issues are synced to PSA project tasks. By default, it is deselected.
  2. [Optional] In the Jira Issue Type field, enter the type of Jira issues PSA projects are synced to. Click to add the Jira issue type to the list.
    Note: If the Jira Issue Type field is left blank, then all issue types will be eligible to import.
  3. [Optional] Select the Sync Jira Comments to PSA checkbox to automatically synchronize Jira comments to the Content Note sObject and be viewable in the Notes Related List in the PSA Project Task. In the Project to Issue mode, Jira comments are synchronized to the Notes Related List in the PSA Project only when the Enable Notes setting is enabled.
  4. [Optional] Select the Sync Jira Attachments to PSA checkbox to retrieve the file attachments from Jira and synchronize to PSA. The supported limit size of the attachment is 5 MB. By default, it is deselected.
  1. Enter the value of the Minimum Hours for Failed Events field. This determines the minimum hours to keep failed Integration Core Queue Events before the next scheduled removal job deletes them. You can enter a value in the range of 1 to 9999. By default, the value is 48.
  2. Enter the value of the Minimum Hours for Successful Events field. This determines the minimum hours to keep successful Integration Core Queue Events before the next scheduled removal job deletes them. You can enter a value in the range of 1 to 9999. By default, the value is 1.
  1. [Optional] Select the Enable PSA Direct for Jira checkbox to activate the connection. By default, the connector is deactivated.
    2. Notes:
    • Before you select the Enable PSA Direct for Jira checkbox, ensure that you have performed the steps to Enable the PSA Direct for Jira and Upgrade PSA Direct for Jira features in the Feature Console.
    • If an error occurs during the activation, the connector shows you an error notification that one or more settings are configured incorrectly and the PSA Direct for Jira option gets disabled automatically.
  2. [Optional] Select the Pause PSA Direct for Jira checkbox to pause the synchronized events in the PSA Direct for Jira connector. By default, the connector is unpaused.
    3. Note: You can only pause events when the PSA Direct for Jira is activated.
  3. [Optional] Select the Sandbox Configured checkbox to configure the connector to the sandbox environment. If deselected, PSA Direct for Jira will not synchronize to or from Jira.

Click Save to save the PSA Direct for Jira settings. Click Restore to restore the settings on the PSA Direct for Jira Settings tab to the saved values on your Salesforce org.

Points to Remember

  • Before your users can start syncing PSA Projects to Jira issues.
  • The Jira Issue Type dependent picklist on the Project Task object is defined with the correct values and properly linked to the Jira Issue Type Category picklist.
  • The Mapping Jira to PSA custom metadata records contains all the required fields in Jira for each of the issue types.
  • The Priority and Status value mappings are configured according to your PSA and Jira applications. For more information, see Customizing the Value Mappings. Note that you cannot log time against a summary or parent task in PSA. This is because time automatically rolls up from the lowest-level child task to the highest-level parent task. For example, you might plan to have a structure like the following:
  • Epic - Story - Sub-task, where Epic is the highest-level project task and Sub-task is the lowest-level project task.
  • Epic - Task, where Epic is the highest-level project task and Task is the lowest-level project task.
  • Bug, where Bug is the highest-level project task and has no child project tasks.