...

Jira Cloud CLI users should update their clients to Release 89.51 or newer to continue to work properly. Some result data related to users returned by the platform will be different and this will show in the CLI output data.

One of the most important changes, is that user references like for reporter, assignee, lead, etc...., must now be done using the Atlassian account id (this is unique user key) associated with the user or the user's full display name or substitute. A substitute could be the user's email address but only if that user has chosen to publicly share that address. Using the account id is the most efficient, otherwise, a lookup needs to be done to convert the name to their actually actual Atlassian account id. Script writers should user use account ids whenever possible. User Identification has a bit more on this topic. 

Confluence Cloud

Platform rollouts expected to started late in Maystarted July 1, 2019. See Atlassian information for the latest from them on this topic. 

Confluence Cloud CLI users should update their clients to Release 89.51 or newer to continue to work properly now and will also need a further update to CLI Release 8. 6 later in May. Some actions are no longer available for Confluence Cloud as Confluence Cloud has not yet provided replacement APIs for the APIs they removed. Once support is returned to Confluence Cloud, the CLI will re-enable those actions. Some result data related to users returned by the platform will be different and this will show in CLI output data. 

One of the most important changes , is that user references like for author and similar , must now be done using the Atlassian account id (a unique id) associated with the user or the user's full display name or substitute. A substitute could be the user's email address but only if that user has chosen to publicly share that address. Using the account id is the most efficient, otherwise, a lookup needs to be done to convert the name to their actually actual Atlassian account id. Script writers should user use account ids whenever possible. User Identification has a bit more on this topic.

...

Earlier this year, other Cloud platform changes were made to force the use of API tokens (in place of passwords) for Cloud API access. Earlier releases of CLI 8.x were modified to support this use. See Authentication options for more information on this topic.

...

1. For some Confluence Cloud API removals, you may see the following if you do not have an updated CLI client:
   1. Remote error: Action disallowed. Response code: 403.
   2. Remote error: Unknown error occurred on server. Response code: 501.
2. If you are NOT using the email address and API token for your user credentials for accessing Cloud sites (see Authentication options), you will likely receive: Remote error: User is not authorized to perform the request. Response code: 401.
3. Even when using an API token, we have cases of 401 errors caused by older API tokens. Generate a new token and try again.

Links

• Authentication options - different authentication requirements for Atlassian access
• User Identification - CLI terminology related to users
• Major Change to Jira Cloud REST APIs are Coming to Improve User Privacy
• Bitbucket Cloud REST APIs are Changing to Improve User Privacy

• Jira Legacy
  server System JIRA serverId 729d679a-302c-339f-958b-015e107badcd key CSOAP-1050

• Jira Legacy
  server System JIRA serverId 729d679a-302c-339f-958b-015e107badcd key JCLI-1471