Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-61361

Replace "accountId" workaround when jira-rest-java-client is updated

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: jira-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      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)

       

        Attachments

          Issue Links

            Activity

            Hide
            warden Radek Antoniuk added a comment -

            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!

            Show
            warden Radek Antoniuk added a comment - 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!

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              sc_rsc Stefan Cordes
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: