...
Platform rollouts expected to start late in May early June 2019. See Atlassian information for the latest from them on this topic.
Confluence Cloud CLI users should update their clients to Release 8.5 or newer to continue to work properly now and will also need a further update to CLI Release 8.6 later expected in Mayearly June. 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.
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
One of the most important changes is that user references 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 actual Atlassian account id. Script writers should use account ids whenever possible. User Identification has a bit more on this topic.
...