Activating PSA Direct for Jira

Once you have configured the PSA Direct for Jira fields and performed any required customization steps, you can activate the PSA Direct for Jira. This is done by enabling the PSA Direct for Jira feature in the Feature Console. For more information, Enabling PSA Direct for Jira Connector.

For more information on using the Feature Console, see Enabling and Disabling Features.

Prerequisites

You must have a Salesforce site domain registered for your org. Feature Console will create a site under your domain. For more information, see Salesforce help for Managing Salesforce Sites.

The user enabling PSA Direct for Jira must have the following permission sets assigned:

  • FDN Core - Mapping
  • PSA Direct for Jira - Configure Jira Mappings
Notes:
  • The user must also have access to the Timecard Entry UI Global custom setting definition.
  • For timecards to be created in PSA, the Salesforce user Automated Process must have the Time Entry permission for the projects and resources the timecards are created against. This must be granted via permission controls. For more information on permission controls, see Permission Controls. For more information on the Salesforce Automated Process user, see the Salesforce Help.

To authenticate a Jira user, depending on the version of Jira you need the following information:

  • Username and password - for Jira Server or Jira Data Center. If your company uses Jira with Single Sign-On (SSO), you must create a non-SSO user for the authentication.
  • Username and API token - for Jira Cloud. For more information on how to generate an API token, see the Jira Cloud Knowledge Base.
Notes:
  • The Jira user must belong to the jira-administrators group and have the appropriate permissions for the feature you enabled. For example, if you want to sync work logs to timecards, the user must be able to view the work logs.
  • After you authenticate the Jira user to the PSA Direct for Jira, you must not change its username in Jira. Doing so will cause the connector to fail. To fix this error, authenticate the user again.

If you switch from Jira Server to Jira Cloud or vice versa after having activated the connector, you must contact Customer Support.