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

Support accountID for AssignIssue step for GDPR

    Details

    • Similar Issues:

      Description

      [Pipeline] jiraAssignIssueWARNING: Unknown parameter(s) found for class type 'org.thoughtslive.jenkins.plugins.jira.steps.AssignIssueStep': accountId
      JIRA: Site - jira - Assigning issue: ABC-24280 to: null
      Successful. Code: 204

        Attachments

          Activity

          Hide
          nrayapati Naresh Rayapati added a comment -

          Can you provide more information, may be with the code snippet that you have?

          I am guessing this is related to:
          https://github.com/jenkinsci/jira-steps-plugin/pull/103

          Show
          nrayapati Naresh Rayapati added a comment - Can you provide more information, may be with the code snippet that you have? I am guessing this is related to: https://github.com/jenkinsci/jira-steps-plugin/pull/103
          Hide
          sachinpali146 Sachin Paliwal added a comment -
          jiraAssignIssue idOrKey: issueId, userName: 'user', site: 'sitename

          It is related to GDPR changes, now we can not use username in Jira api for assigning issue to particular user. In jira-steps-plugin only username can be used for assignment.

          Show
          sachinpali146 Sachin Paliwal added a comment - jiraAssignIssue idOrKey: issueId, userName: 'user' , site: 'sitename It is related to GDPR changes, now we can not use username in Jira api for assigning issue to particular user. In jira-steps-plugin only username can be used for assignment.
          Show
          nrayapati Naresh Rayapati added a comment - PR: https://github.com/jenkinsci/jira-steps-plugin/pull/105
          Hide
          nrayapati Naresh Rayapati added a comment -

          Release 1.5.4, should be available in update center soon.

          https://github.com/jenkinsci/jira-steps-plugin/releases/tag/jira-steps-1.5.4

          Show
          nrayapati Naresh Rayapati added a comment - Release 1.5.4, should be available in update center soon. https://github.com/jenkinsci/jira-steps-plugin/releases/tag/jira-steps-1.5.4
          Hide
          sachinpali146 Sachin Paliwal added a comment - - edited

          Hi Naresh Rayapati,

          Issue is still there in `jira-steps-1.6.0`, when I tried to assign Jira issue with help of assignId value getting below mentioned error.

          JIRA: Site - jenkins - Assigning issue: JENKINS-61132 to: c5db464c72d8d33
           Error Code: 400
           Error Message: {"errorMessages":["'accountId' must be the only user identifying query parameter in GDPR strict mode."],"errors":{}}

          Command:

          jiraAssignIssue idOrKey: 'JENKINS-61132', accountId: 'c5db464c72d8d33', site: 'jenkins'

          Note: Values in Command has been changed to dummy values.

           

          Show
          sachinpali146 Sachin Paliwal added a comment - - edited Hi Naresh Rayapati , Issue is still there in `jira-steps-1.6.0`, when I tried to assign Jira issue with help of assignId value getting below mentioned error. JIRA: Site - jenkins - Assigning issue: JENKINS-61132 to: c5db464c72d8d33 Error Code: 400 Error Message: { "errorMessages" :[ " 'accountId' must be the only user identifying query parameter in GDPR strict mode." ], "errors" :{}} Command: jiraAssignIssue idOrKey: 'JENKINS-61132' , accountId: 'c5db464c72d8d33' , site: 'jenkins' Note: Values in Command has been changed to dummy values.  
          Hide
          vaixe Martin Doucet added a comment -

          Sorry for my boldness, but I'll go head and reopen. The error still occurs with v.1.6.0.

          jiraAssignIssue idOrKey : 'DUMMY-32', accountId : 'hdf7hihgkdugbsigdh'

          results in pipeline error:

          JIRA: Site - Vaixe - Assigning issue: DEMO-6 to: hdf7hihgkdugbsigdh
          Error Code: 400
          Error Message: {"errorMessages":["'accountId' must be the only user identifying query parameter in GDPR strict mode."],"errors":{}}

          The accountID (obviously a dummy here) is the info gathered from the API using:

          https://<instanceURL>/rest/api/2/issue/<ticketId>/
          

          I used as a compare point a different ticket assigned to the user that I want the original to be assigned to. Error is as above.

          Tried userName with either the ID or the user's name, still erroring out.

          Kindly help.

          Show
          vaixe Martin Doucet added a comment - Sorry for my boldness, but I'll go head and reopen. The error still occurs with v.1.6.0. jiraAssignIssue idOrKey : 'DUMMY-32' , accountId : 'hdf7hihgkdugbsigdh' results in pipeline error: JIRA: Site - Vaixe - Assigning issue: DEMO-6 to: hdf7hihgkdugbsigdh Error Code: 400 Error Message: { "errorMessages" :[ " 'accountId' must be the only user identifying query parameter in GDPR strict mode." ], "errors" :{}} The accountID (obviously a dummy here) is the info gathered from the API using: https: //<instanceURL>/ rest /api/2/issue/<ticketId>/ I used as a compare point a different ticket assigned to the user that I want the original to be assigned to. Error is as above. Tried userName with either the ID or the user's name, still erroring out. Kindly help.

            People

            • Assignee:
              nrayapati Naresh Rayapati
              Reporter:
              rakeyshkande Rakesh Kande
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: