Configuring the PSA Direct for Jira Settings

The PSA Direct for Jira integration 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.

  1. Click the PSA Direct for Jira Settings tab.
  2. [Optional] In the Integration Settings:
    1. Enter the email address that will receive error notifications if the relevant resource does not have an email address, for example, if the integration fails to synchronize a task.
    2. Select Use Parent Link 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 disabled.
  3. Depending on the project requirement, in the project settings:
    1. Enable 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.
    2. Select Jira Projects or Jira Issues to map PSA Projects.
    3. If you have selected to synchronize to Jira Issues:
      1. Enter the name of the issue type. For example, Epic.
      2. Enable the Update PSA Project based on Jira Issue option to ensure that the eligible PSA projects are updated based on Jira issue. By default, it is disabled.
    4. Note:

    If the integration is enabled, and you have a saved value in the PSA Direct for Jira custom setting for the Jira Projects radio option in the Project Settings component, and you change your selection, then updates would stop for all synchronized projects.

  4. [Optional] In the Project Task Settings, enable the Sync PSA Project Tasks to Jira Issues option to ensure that the eligible PSA project tasks are synced to Jira issues.
  5. [Optional] If you have selected to sync PSA Project with Jira Issues, 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.
    1. Select Update Projects based on Issue to ensure that the eligible PSA projects are updated based on Jira issue status.
    2. 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.
    3. 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.
  6. In the Timecard Settings, select the value of the Timecard Status field. This determines the status in which the integration 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, if you deactivate or delete the value from the picklist on the Timecard object, the setting is not updated.

  7. In the Jira Issue Type Settings:
    1. Enable the Sync Jira Issues to PSA Project Tasks option to ensure that the eligible Jira issues are synced to PSA project tasks.
    2. In the Jira Issue Type field, enter the type of Jira issues PSA projects are synced to. The default value is Epic. 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.
  8. In the Cleanup Queue Events Settings:
    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.
  9. [Optional] Enable the PSA Direct for Jira option to activate the integration. By default, the integration is deactivated.
    Notes:
    • Before you enable the PSA Direct for Jira option, ensure that you have performed steps in Enabling the PSA Direct for Jira and Upgrading PSA Direct for Jira features in Feature Console.
    • If an error occurs during the activation, the integration shows you an error notification that one or more settings are configured incorrectly and the PSA Direct for Jira option gets disabled automatically.
  10. [Optional] Enable the Pause PSA Direct for Jira option to pause the synchronized events in the PSA Direct for Jira integration. By default, the integration is unpaused.
    Note: You can only pause events when the PSA Direct for Jira is activated.
  11. Click Save.

Points to Remember

  • Before your users can start syncing PSA projects to Jira issues, you must manually edit the Jira Project picklist field on the Project object. You must add the Jira project keys of all the projects you want to create issues against as picklist values.
  • 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 in PSA you cannot log time against a summary or a parent task. 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.