The query parameter 'username' is not supported in GDPR strict mode about connector-jira HOT 6 CLOSED

Dear @leonelfolmer

I am using cloud version of jira & jira servicedesk & confluence, ...

I have the same issue regarding the username since GDPR.

I found this : https://community.atlassian.com/t5/Advanced-Roadmaps-questions/error-quot-The-query-parameter-username-is-not-supported-in-GDPR/qaq-p/1365942

By 29 April 2019, we will remove personal data from the API that is used to identify users, such as username and userKey, and instead use the Atlassian account ID (accountId). Additionally, will be restricting the visibility of other personal data, such as email, in conjunction with a user's profile privacy settings.

and the migration link : https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/

It will be great if the owner could update the "accountID" instead of "username".

Best Regards

from connector-jira.

We are currently not using cloud version of jira. We are not impacted by it for the moment. If anyone is going to work on this, would it be possible to keep a backward compatibility to old api calls?

from connector-jira.

The Jira Python library has just been updated to accomodate the necessary changes. But it is still not part of any stable release of the library.

Here is the commit.

If anyone is looking to work on this one, first thing would be to help test that versions > 3.0.1 of the library work well with the connector_jira addon.

By the way, the lib changes are backward compatible :).

from connector-jira.

It seems there is no way to link users in automatic mode with cloud Jira. There is no emailAddress or Login (username) information anymore in the response, only accoundId

There is displayName which is in my opinion is unreliable to be used for linking

from connector-jira.

So I think the only way here - to link users manually or with help of some sort of Identity Provider

from connector-jira.

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

from connector-jira.