New Features and Enhancements in PSA Direct for Jira Spring 2022
The following new features have been introduced in the Spring 2022 release of PSA Direct for Jira.
If you are upgrading from a previous version, see Upgrading to PSA Direct for Jira Spring 2022. This provides a summary of the items that have been added for each feature and details of any required upgrade steps.
Dependencies on other FinancialForce Packages
This release of PSA Direct for Jira requires the following FinancialForce packages to be installed:
- FinancialForce Foundations Spring 2022
- FinancialForce PSA Spring 2021
- FinancialForce PS Enterprise Spring 2021
You must install these packages before installing or upgrading to this release of PSA Direct for Jira.
URL Link from PSA Project to Jira Project
We have added a Jira Project URL field to the PSA Project object to open the related project or issues in Jira. This replaces the similarly named field in PSA that is no longer needed for PSA Direct for Jira integration.
The Jira Project URL field is a read-only field that provides a hyperlink to the corresponding project in Jira. After you synchronize the PSA project to the Jira project, 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 corresponding project in PSA. In case of any failure with the hyperlink to open the related project or issues in Jira, it is recommended to you that you perform step 3 of the Upgrade PSA Direct for Jira feature in the Feature Console. For more information, see Upgrading PSA Direct for Jira Integration.
For more information, see:
- Upgrading PSA Direct for Jira Integration
- Synchronizing PSA Projects to Jira
- Creating a Jira Project from a PSA Project
- Creating a Jira Issue from a PSA Project
- Project Fields
Support for Jira Template Projects
A new Jira Project Template field is added to the PSA Project object. This allows you to select an existing Jira Project that will be cloned to create a new Jira project that represents the PSA project when synced.
For more information, see:
- Upgrading PSA Direct for Jira Integration
- Synchronizing PSA Projects to Jira
- Creating a Jira Project from a PSA Project
- Project Fields
Allow Selection of Jira Template to Create Jira Projects
You can now select the Jira template applied when creating projects. To do so a new Jira Template field is added to the PSA Project object. You must select a Jira Template or use a Jira Template Project to create a project.
For more information, see:
- Upgrading PSA Direct for Jira Integration
- Synchronizing PSA Projects to Jira
- Creating a Jira Project from a PSA Project
- Project Fields
Support Jira Complex Fields as Objects
Prior to this release, PSA Direct for Jira custom field mapping only supported simple fields like string, number, and date from Jira. In this release, PSA Direct for Jira now supports using custom metadata records to define objects for custom fields in Jira, allowing support of complex fields from Jira such as drop-downs for Jira Issues synchronized to or from PSA project tasks.
The newly created custom metadata records describe the structure of Jira objects to use when customizing PSA Direct for Jira field mappings.
For more information on creating new custom metadata records to support Jira custom fields, see
Manage PSA Direct for Jira Queue Messages
PSA Direct for Jira integration provides you with a FDN Manage Queue Status Lightning component available in Foundations allows you to control the message queue events from PSA Direct for Jira to Atlassian Jira and vice-versa. A new PSA Direct for Jira Queue Status tab is added to view and manage the detailed message information.
For more information, see:
- Upgrading to PSA Direct for Jira Spring 2022
- PSA Direct for Jira Queue Status
- PSA Direct for Jira Queue Status Fields
Language Packs
PSA Direct for Jira now supports the translation of the user interface text. This enables you to translate and view the user interface text based on your specified languages.
The following language packs are available for PSA Direct for Jira Spring 2022:
- Danish
- Dutch
- French
- German
- Hebrew
- Italian
- Japanese
- Korean
- Norwegian
- Simplified Chinese
- Spanish
- Swedish
Adding Custom Translations
You can translate the custom labels of PSA Direct for Jira integration. This allows you to view the user interface text labels in various languages. PSA Direct for Jira does not include any translations as part of the managed package.
- Use the Translation Workbench, a feature of the Salesforce platform, to override the packaged custom labels with translated versions. The Translation Workbench is an optional feature only available in multi-language orgs. For more information about setting up the Translation Workbench, see the Salesforce Help.
- Ensure that your users' language settings align with the translated custom labels you want them to see.
To find out more about Language Pack and Translation Reporter, see Translation Reporter Overview.
Fixes
Fixes are listed on the Known Issues page of the FinancialForce Community. You can access this page from the Community Support Hub. For a brief description of the issues that have been fixed in this version of PSA Direct for Jira, see the relevant section of the Known Issues page.