Assignee and reporter fields after gdpr changes

[Mia Simundic]

Hi,

With username parameter we are searching for assignee and reporter, and this is not possible any more.

How we can handle Jira assignee and reporter fields after gdpr changes? What information is possible to put in those fields now instead of username? What will be with those fields in the future?

BR/Mia

[John Funk · Accepted solution]

Hi Mia - Can you provide some more context? Where are you searching? What are you not able to do?

[Mia Simundic]

Hi John,

gdpr changes for username parameter affected our application.

I'm using jira rest client api 5.1.0 (Also this is checked on latest version 5.2.1 and I don't see any way to find user and fill assignee field on backend).  Due to GDPR change I have a problem with search user.

This is method which I use from client api 5.1.0 : 

Promise<Iterable<User>> findUsers(String username, @Nullable Integer startAt, @Nullable Integer maxResults,
        @Nullable Boolean includeActive, @Nullable Boolean includeInactive); 


GET path/search?searchTerm=mar

Response: 

{    "statusCode": "ERROR",   
 "message": "java.util.concurrent.ExecutionException: com.google.api.client.http.HttpResponseException: 400\n{\"errorMessages\":[\"The query parameter 'username' is not supported in GDPR strict mode.\"],\"errors\":{}
}"


So if it is not possible to find user using username any more, what will be with assignee field, how can I assign user on ticket if I cannot search user by it's username?

BR

[John Funk]

You should probably go ahead and submit a support ticket here:

https://support.atlassian.com/contact/#/

[Achyutha]

Im facing similar issue, please help. Was this solved?