Privacy changes to Jira issue/* REST API endpoints

Description

As documented in the notice to Jira Cloud API developers regarding upcoming changes to protect user privacy, we are introducing significant changes to Jira Cloud REST APIs to remove private user information.

At a high level, these changes will include changes to the shape of user objects in the Jira Cloud REST APIs and the replacement of userKey and username parameters with accountId.

Follow this ticket for specific information about changes and applicable dates to the following endpoints:

Endpoint

Methods

/api/2/issue/{issueIdOrKey}

POST, PUT

/api/2/issue/{issueIdOrKey}/watchers

POST, DELETE

Environment

None

Activity

Show:
Ben Kelley
December 3, 2018, 10:25 PM

Thanks for that . I have raised a bug report to track this at https://jira.atlassian.com/browse/JRACLOUD-71154

Hiten Prajapati
December 3, 2018, 10:59 AM
Edited

what about /issue/{issueIdOrKey}/notify?

i have request for user like.
"to": {
"users": [
{
"name": "admin"
}
]
}

i try with accountId or id. It's gives me internal server error.

Ben Kelley
November 7, 2018, 3:34 AM

These changes have now been rolled out.

Ben Kelley
November 7, 2018, 3:33 AM

As discussed in your other ticket, when specifying user fields for issue create/update, you can use "id" (not "accountId") to specify users by account ID, rather than "name" to specify them by user name.

I'm going to mark this ticket as closed.

If you find that there are things that don't work the way you expect, can I ask that you create a support ticket for that. This way our support team can keep track of outstanding problems.

Kevin Chen
November 1, 2018, 3:42 PM

My apologies. Only the PUT has problems. GET is fine. Just misread the JSON.

Fixed

Assignee

Unassigned

Reporter

Dave Meyer

Labels