Synchronizing PSA Projects to Jira

Notes:

• For a project to be synced to Jira, the Project Name and Jira Project Key fields must be populated with unique values.
• A project template (a project that has the Template field selected) cannot be synced with Jira.
• The project manager (contact) record must be correlated with a Jira user before the project is synced. For example, if you create the contact record while creating the project in PSA, it might not sync to Jira before the project, causing an error.
• If a value is selected for Jira Project Type you must also select a value for Jira Template. You can choose one of the templates available in Jira to create a PSA Project that uses a predefined template provided by Jira.
• If you select a value from the Jira Project Template field to create a PSA project cloned from an existing Jira project, you cannot choose a value from the Jira Project Type field.
  • You can choose either a Jira Project Type field or a Jira Project Template field. But, you cannot have both selected.
• You cannot select both the Jira Project Template and Jira Template fields simultaneously.

When you create a new project in PSA, the integration creates a new Jira project with the information listed below. Similarly, when you edit an eligible project in PSA, the integration updates the related project in Jira.

Key: * – Mandatory field.

PSAProject Field	Jira Project Field
Project Name *	Project
Jira Project Key *	Key
Jira Project Type *	Project type
Project Manager *	Project lead
Notes	Description

Note:

It is recommended that you do not change or remove access to Jira site for Jira Project Lead. If you do so and create a new Jira project task for that Jira Project, then the PSA user who created or updated the project tasks receives an email notification, and a Foundation's error message is created.

For more information on modifying the default mappings or creating custom mappings, see Customizing PSA Direct for Jira Field Mappings.

The Jira Project Type determines which template is used to create the new project in Jira:

• "Software" - the new project is created using the Basic software development template.
• "Business" - the new project is created using the Task management template.

The Jira Project Template determines which project in Jira is used as a template to create the new project. Whereas, Jira Template allows you to create a PSA project which uses a predefined template provided by Jira.

Note:

The project is created as a classic project in Jira. Next-gen projects are not supported.

After a project is created in Jira, the Jira Correlation ID field is automatically populated in PSA. You must not change this value unless you are manually correlating existing projects. For more information, see Linking Existing PSA and Jira Records.

Once a project is synced, the Jira Project URL field in PSA populates with a hyperlink to the related project in Jira. Similarly, the URL field for the project in Jira is populated with a hyperlink to the related project in PSA.

Notes:

• Once a project is created in Jira, its type cannot be changed from PSA. If you change the project type, you must do so manually in both applications.
• Jira projects are not deleted if the project is deleted in PSA, the Active field is deselected or the Closed for Time Entry field is deselected in PSA. If you delete a Jira project created by the integration, you must do so manually in Jira.

If an error occurs during the synchronization, the PSA user who created or updated the project receives an email notification and a Foundations error message is created.

Instead of syncing PSA projects to Jira projects, you can choose to sync projects to issues. This can be useful if your PSA projects tend to be smaller and shorter than a typical Jira project, or if you are using a separate Jira project for each team in your Professional Services department. The integration can create a parent level issue type in Jira, for example, an epic. Once the parent level issue is correlated with PSA, work logs created for the child issues, for example, tasks or user stories, automatically create PSA timecards.

You can configure the type of Jira issue PSA projects are synced to. For more information, see Configuring the PSA Direct for Jira Settings.

If you enabled syncing PSA projects to Jira issues via the PSA Direct for Jira Settings tab, eligible projects are automatically synchronized to Jira. A project is eligible for syncing if the Sync with Jira checkbox is selected.

Notes:

• For a project to be synced to a Jira issue, the Jira Project field must be populated. You must manually add the Jira project keys of all the relevant projects to the Jira Project picklist.
• A project template (a project that has the Template field selected) cannot be synced with Jira.

When you create a new project in PSA, the integration creates a new Jira issue with the information listed below. Similarly, when you edit an eligible project in PSA, the integration updates the related issue in Jira.

Key: * – Mandatory field.

PSAProject Field	Jira Issue Field
Project Name *	Summary
Jira Project *	Project Key

Note:

Before you can create Jira Epics from PSA, you must update the PSA to Jira Issue Fields custom metadata. The field IDs for Epic Name and Epic Link are specific to your Jira environment. PSA Direct for Jira provides default metadata records but you must update these with the specific Jira custom field details for your environment.

For more information on modifying the default mappings or creating custom mappings, see Customizing PSA Direct for Jira Field Mappings.

After an issue is created in Jira, the Jira Correlation ID field is automatically populated in PSA. You must not change this value unless you are manually correlating existing projects and issues. For more information, see Linking Existing PSA and Jira Records.

Once the issue is created, the Jira Project URL field in PSA populates with a hyperlink to the related issue in Jira.

Notes:

• If the Jira Project field is changed in PSA, the related issue is not moved to another project in Jira.
• Jira issues are not deleted if the project is deleted in PSA, the Active field is deselected or the Closed for Time Entry field is deselected in PSA. If you delete a Jira issue created by the integration, you must do so manually in Jira.

If an error occurs during the synchronization, the PSA user who created or updated the project receives an email notification and a Foundations error message is created.