Skip to content

Conversation

janoskut
Copy link
Contributor

According to https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-user-properties/#api-group-user-properties, the user identifier for user property endpoints is "accountId", not "username".

This fixes the API for the endpoints:

  • Get user property keys
  • Get user property
  • Set user property
  • Delete user property

According to https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-user-properties/#api-group-user-properties, the user identifier for user property endpoints is "accountId", not "username".

This fixes the API for the endpoints:
- Get user property keys
- Get user property
- Set user property
- Delete user property
@gonchik
Copy link
Member

gonchik commented Feb 14, 2022

Looks like we have to support both way, as wrapper used for the on-premises solutions which is mostly for the Server/Data Center releases

@gonchik gonchik merged commit 39c4478 into atlassian-api:master Apr 28, 2022
gonchik pushed a commit that referenced this pull request Sep 3, 2022
According to https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-user-properties/#api-group-user-properties, the user identifier for user property endpoints is "accountId", not "username".

This fixes the API for the endpoints:
- Get user property keys
- Get user property
- Set user property
- Delete user property

Co-authored-by: Janos Kutscherauer <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants