[JIRA] (JENKINS-61361) Replace "accountId" workaround when jira-rest-java-client is updated

[rsc@adr.de (JIRA)]

Stefan Cordes created an issue

Jenkins / JENKINS-61361 Replace "accountId" workaround when jira-rest-java-client is updated Issue Type: Improvement Assignee: Unassigned Components: jira-plugin Created: 2020-03-06 09:12 Priority: Minor Reporter: Stefan Cordes With JENKINS-56987 (Pull Request https://github.com/jenkinsci/jira-plugin/pull/213 ) one line in  hudson.plugins.jira.JiraRestService.createIssue(String, String, String, Iterable<String>, String, Long, Long) needed to use a workaround to set "accountId" instead of "name".   When the GDPR changes are fully merged in jira-rest-java-client (probably version 5.2.2) https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/104/change-field-name-from-name-to-accountid the workaround can be changed back to builder.setAssigneeName(assignee) (or builder.setAssigneeAccountId(assignee) depending on the provided solution)   Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[radek.antoniuk@gmail.com (JIRA)]

Radek Antoniuk commented on JENKINS-61361

Re: Replace "accountId" workaround when jira-rest-java-client is updated Stefan Cordes would you mind creating a Pull Request for this so that it just sits and waits for the needed dependencies? that would be really helpful, thank you!

Add Comment