Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Username removed from view | What happens to rest api

subodhonline
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 2, 2018

I am working on project which creates jira issue using rest api and assign it to a group member.

{ "fields": { "project": { "key": "CON" }, "summary": "REST ye merry gentlemen.", "description": "Creating of an issue using project keys and issue type names using the REST API", "issuetype": { "name": "Bug" }, "assignee":{ "name":"username" } } }

Our organization is using jira for long time.

So most of the people forgot their username they just login usning email.

Now the problem is Atlassian has removed username display from user management and most of the peeps forgot their username.

"We don't display usernames anymore as part of unifying user profiles across all Atlassian Cloud products."

Now what I can do to assign tickets? Please help me

1 answer

0 votes
Angélica Luz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 3, 2018

Hi Subodh,

These changes were made to protect customers' and users' personal information and this is due to [General Data Protection Regulation (GDPR)|https://www.atlassian.com/blog/announcements/atlassian-and-gdpr-our-commitment-to-data-privacy].
Now, instead of using the username, you can use the accountID.
To find the accountID you must go to https://xxxxx.atlassian.net/people/search and open the user profile. The ID will show in the URL after the /people/.

You can find more information about these changes on the documentation below:

Major changes to Jira Cloud REST APIs are coming to improve user privacy

Updates to APIs which accept user name or key as input
A number of Jira API endpoints currently accept Jira user names as path parameters, query parameters, or in request bodies. Jira will introduce new versions for each affected API that accepts the username or userKey parameters. In all cases, requests that previously used a user name or user key will only accept an accountId in the new API version.

That API document should also include a number of update tickets that you can follow regarding this functionality as well:

ACJIRA-1511 - Privacy changes to Jira username values in REST API endpoints

ACJIRA-1497 - Privacy changes to Jira user/* REST API endpoints

 

Hope this helps.

If you need further assistance, please let us know.

Regards,
Angélica

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events