jira: Unable to self-assign issues with jira cli
I’ve been using the jira cli as part of custom commands I run on my system to simultaneously create a branch based on the ticket name, assign it to myself in Jira, and move the issue to In Progress. Until recently, it has been working quite well. I was on vacation for a few weeks, and upon my return it has stopped working.
- Whenever I run
jira view TICKET_ID, it returns the ticket details fine - Whenever I run
jira take TICKET_ID, I get the following error:
ERROR Invalid Usage: 'accountId' must be the only user identifying query parameter in GDPR strict mode.
I have been playing around with my API tokens (which are stored in keyring on a Macbook), and .jira.d/config.yml to see if I can isolate the cause and, along with the error message, have determined the following:
- The new system JIRA is rolling out for GDPR requires using the
accountIdfield as a replacement of theuserfield for requests. I have since updated my config to include myaccountId - The jira cli will not allow a login using an API token without at least one of the
userorloginfields- If I remove this field from my config, it incorrectly registers which user I am (thus implying that the
accountIdfield is not working for identification purposes)
- If I remove this field from my config, it incorrectly registers which user I am (thus implying that the
My current .jira.d/config.yml contains the following fields (that have been anonymized):
endpoint: https://mycompany.atlassian.net
accountId: MY_PROFILE_ACCOUNT_ID
user: patrick@mycompany.com
password-source: keyring
My guess is that the user and login fields are also the culprit to the GDPR based message, simply because it is complaining that user identifying query parameters are being passed in to the API request.
Is someone able to explain what I am doing wrong, and/or the correct fix for this? I really really like my personal tooling as it increases my productivity, and decreases the repetitive mundane tasks I need to do on a regular basis, and would really appreciate being able to use them again.
Thanks
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 26 (16 by maintainers)
The latest release, as well as the one I compiled myself, does not seem to work for me:
Related: https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/
They removed
usernameanduserkeyfrom the API entirely. You HAVE to now useaccountIdfor everything