Upgrading to PSA Direct for Jira Summer 2026
This page describes the changes to make when upgrading to Summer 2026.
See the Upgrade Steps section under each feature for details of any action required. If you don't want to use or upgrade an optional feature, you can skip the upgrade steps for that feature. To perform upgrade steps in your org, you must be assigned administrator permissions.
See the Included in This Feature section under each feature for details of items such as objects, fields, or buttons that have been added in this release.
If you are upgrading from a version earlier than Winter 2026, check the documentation for previous releases for upgrade details.
For information on new features and changes to existing features in Summer 2026, see New Features and Enhancements in PSA Direct for Jira Summer 2026.
Prevent Duplicate Jira Issues When Making Bulk Updates from PSA
Upgrade Steps
To upgrade this feature to Summer 2026, take the following action.
| Step | Action | Further Information |
|---|---|---|
| 1. | Create a custom field in Jira to store the Salesforce record ID. For more information about creating custom fields in Jira, see the Atlassian documentation. | Creating Custom Metadata Records to Support Different Jira Custom Fields |
| 2. | On the PSA Direct for Jira Settings, specify the Jira custom field that stores the Salesforce record ID, and enable the feature. | PSA Direct for Jira Settings |
Included in This Feature
This section details the items that have been added, updated, or deleted in this release.
Custom Setting Fields
| Custom Setting Field | Custom Setting | Further Information |
|---|---|---|
| Correlate in Jira | PSA Direct for Jira Settings | PSA Direct for Jira Settings |
| Jira Correlation Field |
SECTIONS