Hi everyone,

We're closing this request as a duplicate of ACCESS-577, which will provide an improve audit log of user managements across Atlassian Cloud sites (including user invitations and changes to group memberships). We consider API access for this audit log within the scope of that issue, so when it is available, we will announce it there.

We're closing this issue because the scope of the request is specifically around an API for reporting on changes. If you are interested in an API for managing users and groups in Jira Cloud, we're pleased to announce that documentation for the User provisioning (SCIM) API is now available on developer.atlassian.com. The API is an implementation of the SCIM specification and is intended to be used to sync users and groups from an identity provider to an Atlassian organization. Once you have linked an Atlassian Cloud site (like example.atlassian.net) to your organization, users and groups will be synced to your site and you can use them to control access to Jira and Confluence Cloud as well as permissions within those products. Learn more about how automatic user provisioning works with Atlassian Cloud.

There are several key benefits to automating user provisioning for Atlassian Cloud:

• It saves you time as an administrator by automating the process of creating and removing Atlassian accounts for your users
• It improves security by reducing errors in the provisioning/deprovisioning process
• It can help reduce costs by ensuring you are not billed for users who are no longer active

The SCIM API is intended for customers who are not already using one of our supported identity providers. We currently support Okta and are actively working on support for Azure Active Directory and Onelogin. If you are using one of these identity providers, we recommend using the supported Atlassian app for these identity providers as this will simplify the configuration process.

We're actively working in this area and will share another update on the SCIM API feature request (ID-6305) when support for additional identity providers is available.

Regards,
Dave Meyer
Atlassian Access Product Management

Hi varsha.mane976916654,

The update user experimental API in JIRA Cloud has recently been removed. Please see https://jira.atlassian.com/browse/JRACLOUD-66936?focusedCommentId=1609545&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1609545 for details.

Thank you,

Diego

Hi Diego

As per latest https://docs.atlassian.com/jira/REST/cloud/  document, update user api not found.

https://docs.atlassian.com/jira/REST/cloud/#api/2/user-updateUser this api not found in document.

Can you please confirm that update user is not supporting in future?

Thanks

Varsha

Hi Diego

I have this issue as well, https://jira.atlassian.com/browse/JRACLOUD-67118 but this issue is for group add and remove users.

I have issue to delete group https://jiracloudconnect.atlassian.net/rest/api/2/group?groupname=Ylgdprlqcw

We are facing error while deleting group.
Error Code: 400 with
{"errorMessages":["Cannot delete group, as all directories are read-only."],"errors":{}}

Thanks
Varsha

Hi varsha.mane976916654, I'm sorry to hear that you are still having problems with JIRA's REST API. It is possible that error has the same root cause as https://jira.atlassian.com/browse/JRACLOUD-67118 . Please watch or comment on that issue.

Thank you.