jira: jira create stopped working

Getting the following since yesterday:

MacBook-Pro :: ~ % jira create                                                                                                                                                           
ERROR The query parameter 'username' is not supported in GDPR strict mode.
? Jira reported an error, edit again? (Y/n)

my config.yaml has the following:

endpoint: https://<work>.atlassian.net                                                                                                                                               
user: rattboi                                                                                                                                                                   
login: <my work email>                                                                                                                                                      
jira-deployment-type: cloud                                                                                                                                                           password-source: keyring                                                                                                                                                              
issuetype: Story                                                                                                                                                                      
project: IO                                                                                                                                                                           
priority: P2

I’m running latest release: 1.0.23

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 17
Comments: 19

Most upvoted comments

Similar seems to be happening with jira assign and jira take

wolgastj on Apr 17, 2020

Just figured out a workaround by editing templates.

Looking at the template used by the create command you’ll see:

  reporter:
    name: {{ or .overrides.reporter .overrides.user }}

Replace name with id so it becomes:

  reporter:
    id: {{ or .overrides.reporter .overrides.user }}

Now in your config.yml set the override:

overrides:
  reporter: <your user id here>

And you should be set! There may be other templates that need to be modified as well, I’ll take a look and take a crack at a PR.

bradym on May 19, 2020

okay that issues dups: https://github.com/go-jira/jira/issues/369

closing this and lets track that problem in 369

ldelossa on Sep 4, 2020

Hello, I had this issue today while creating a new issue. My case was related to the reporter field (which is mandatory it seems), that in the YAML template is:

fields:
  reporter:
    name: f.bar

I’ve been able to fix it by replacing name with id, taking my account number from the profile page URL (as in https://community.atlassian.com/t5/Jira-questions/where-can-i-find-my-Account-ID/qaq-p/976527).

It’s really painful clearly, so I’ll be looking around for a better solution.

PS: thanks for the work that went into this CLI, it really shines 👍

endorama on May 14, 2020

Did a bit of tracking down today. The fix in #317 tries to convert a user name to an account ID by using /rest/api/2/user/serach?username=<username>. But it looks like that doesn’t work anymore, since hitting it on jira cloud gives:

{“errorMessages”:[“The query parameter ‘username’ is not supported in GDPR strict mode.”],“errors”:{}}

Could probably switch over to “query=”. The query value matches against both the “displayName” and “emailAddress” fields.

Follow up: replacing “name” with “emailAddress” (with appropriate value) works for creating issues.

robertdzeigler on Apr 29, 2020