Enabling PSA Direct for Jira Integration
To enable the integration, perform the following steps:
- On the Feature Console tab, click PSA Direct for Jira.
- Ensure that you create named credentials to allow PSA users access to the Jira server. To do this:
- Click Launch next to feature step 1. The Jira Authentication dialog displays.
- Enter your Jira Server URL. For example, enter the following:
- Jira Server URL - https://test.com/
- Jira Cloud URL - https://subdomain.atlassian.net/
- Depending on the version of Jira you are using, select Jira Cloud or Jira Server.
- Enter your Jira username.
- Depending on the version of Jira you are using, enter your password or API token.
- Click Save. When the save successfully completes, the step status is set to "Done".
- Click Perform next to feature step 2. This step creates a Certinia Integrations site and profile and configures settings to enable the connection between Jira and PSA.
- Click Perform next to feature step 3. This creates a webhook in Jira that integrates Jira with PSA Direct for Jira. When the process completes, the status is set to "Done".
- Click Perform next to feature step 4. This creates default data transformation tables for value mappings. The tables are created in Foundations, and you can edit the defaults. When the process completes, the status is set to "Done". If you revert this step the tables are deleted. The data transformation tables are used to transform values from PSA to the appropriate Jira values or vice-versa. For example, priority P1 in PSA is mapped to Highest in Jira. Whereas, priority Highest in Jira is mapped to P1 in PSA. You can also manually create Data Transformation Tables. For more information, see Creating a Data Transformation Table.
- Click Perform next to feature step 5. This creates a Foundations message type for recording error messages. When the process completes, the status is set to "Done". If you revert this step, Foundations marks the message type as obsolete. For more information, see Message Types Overview.
- [Optional] Click Perform next to feature step 6. This creates a scheduled job to regularly delete queue events. By default, the Queue Events Cleanup Job is run on the hour once you have performed this step. When the Queue Events Cleanup Job is created the status of the step is moved to "Done".
If you revert this step, then it removes the scheduled job. For more information about the Queue Events fields, see Minimum Hours for Failed Queue Events and Minimum Hours for Successful Queue Events.
- [Optional] Click Perform next to feature step 7. This starts a background process that selects the Use for Syncing Time from Jira field on all the eligible assignments. When the background process is started, the status of the step is moved to "Done". For more information, see Monitoring Default Assignments for Jira Batch Jobs.
- [Optional] Click Perform next to feature step 8. This adds the PSA Direct for Jira section and all the integration fields to the Assignment Layout page layout on the Assignment object.
- [Optional] Click Perform next to feature step 9. This adds the PSA Direct for Jira section and all the integration fields to the Project Layout page layout on the Project object. We recommend that you manually remove the fields that are not relevant for the features that you enabled.
- [Optional] Click Perform next to feature step 10. This adds the PSA Direct for Jira versions of the Jira Project URL field and all the integration fields to the PSA Direct for Jira section on the Project Layout page layout on the Project object. We recommend that you manually remove the fields that are not relevant for the features that you enabled.
- [Optional] Click Perform next to feature step 11. This adds the PSA Direct for Jira section and all the integration fields to the Project Task Layout page layout on the Project Task object. We recommend that you manually remove the fields that are not relevant for the features that you enabled.
- [Optional] Click Perform next to feature step 12. This adds the custom fields to the PSA Direct for Jira section on the Project Task Layout page layout on the Project Task object. We recommend that you manually remove the custom fields that are not relevant for the features that you enabled.
- [Optional] Click Perform next to feature step 13. This adds a Child Jira Issues related list to the Project Task Layout page layout on the Project Task object. We recommend that you manually remove the fields that are not relevant for the features that you enabled.
- [Optional] Click Perform next to feature step 14. This adds the PSA Direct for Jira section and all the integration fields to the Contact page layout on the Contact object.
- [Optional] Click Perform next to feature step 15. This adds fields to the Gantt Columns fieldset. For more information, see Adding Columns to the Gantt Task Grid.
- [Optional] Set the platform event user that runs the process information from Jira to PSA. To do this:
- Click Launch next to feature step 16. The Platform Event Trigger Execution dialog displays.
- Enter at least three characters in the Platform Event User field to search the user. For example, enter Platform Integration User.
- Click Save to execute the Platform Events to synchronize the information from Jira to PSA.
- Click Clear to clear the platform event user.
- Once you have complete all the steps, you can manually manage the platform event user subscription:
- From Setup, click Platform Events | FND Internal Event.
- In Subscriptions, Click Manage against the ihcc_PlatformEventTrigger.
- Click Suspend to suspend the platform event subscription.
- Click Resume to resume the the platform event subscription.
- When all steps are complete, use the Status slider in the Feature section to mark the feature as enabled.
To fully activate PSA Direct for Jira, review and complete the fields on the PSA Direct for Jira Settings tab.