Version 9.4.0.0

PSLink Server

Site Configuration

For Jira systems, there is a new dropdown to select the Jira system type (Cloud or Server/Data Center). This is required as Jira Cloud allows usage of custom domains, so it is not possible to automatically detect the type from the URL alone.

We'll try to detect the type automatically on upgrade based on the URL. However, this will yield an incorrect result if you are using a custom domain for Jira Cloud. Please double-check your site configurations after upgrading.

SiteConfiguration3

PSLink Standalone Client

Logging in to sites with Project Online systems where the tenant administrator configured a Conditional Access Policy with device requirements failed in previous versions, because we did not enable Device ID handling on the WebView2 control. This is remediated in the new release, and users can now log in successfully when such policies are in place.

Old Login

TPG PSLink 9.3.1.0 and before: Entra ID login does not recognize the Windows user account.

New Login

TPG PSLink 9.4.0.0: Entra ID login proposes the Windows user account automatically.

 

Atlassian Jira connector

We've updated our Jira connector to use the latest Jira REST API version 3 for Jira Cloud systems!

We had to make some breaking changes to achieve this. These apply to Jira Cloud systems only!

Jira Server/Data Center systems will continue to use the REST API v2 and are not affected. Some changes were unavoidable due to the API changes.

GetJiraIssues action

Previously, our GetJiraIssues action allowed a "minimum configuration" which made it retrieve all issues the user has access to. This is no longer possible with the new API, so you must now set either the projectIdOrKey or jqlQueryString input property.

Another breaking change affects the Description column of the issues output table. The REST API v3 does not return the description as plain text anymore, but as a JSON string in a format called Atlassian Document Format (ADF). We're handing this JSON string as-is to you.

The change from plain text to JSON (ADF) also applies to multi-line custom fields. These fields are still added as columns to the issues output table, but they are in ADF now.

GetJiraWorkLog action

The REST API v3 does not return the Author and UpdateAuthor fields Name, Key, and EmailAddress anymore. As a replacement, we're now handing out the AccountId, so that gives you at least a way to identify the user and group the data.

Additionally, the work log field Comment is now also a JSON string (ADF) instead of plain text, just as in GetJiraIssues described above.