Description

We always are sensitive to upward compatibility of our offerings and specifically want to make sure CLI scripts are as upward compatible as possible at least with the respect to those aspects that are under our control. Most of our actions remain compatible across a wide range of Atlassian application releases and even to high degree across Server and Cloud environments. However, on a CLI version boundary, we do take the opportunity to remove previously deprecated support or make some changes especially where it will simplify new user experiences and remove clutter for users. This page describes some of the important changes to be aware of when upgrading to 10.x from 9.x or earlier.

Client changes

Client	Change	Replacement	Discussion

Client	Change	Replacement	Discussion
servicedesk	renamed	jsm	The servicedesk client has been renamed to jsm to correspond with Atlassian's renaming Jira Service Desk to Jira Service Management.
structure	removed		Support has been removed.

Removed actions

Clients	Removed	Replacement	Discussion

Clients	Removed	Replacement	Discussion
bitbucketcloud	team actions	workspace	Bitbucket Cloud removed support for a number of legacy terms and changed ownership relationships with workspaces becoming the key concept.
jira	deleteScreen	removeScreen	Consistency as opposite of addScreen.

Removed parameters

Clients	Removed	Replacement	Discussion

Clients	Removed	Replacement	Discussion
bitbucketcloud	team	workspace	Bitbucket Cloud removed support for a number of legacy terms and changed ownership relationships with workspaces becoming the key concept.
bitbucketcloud	owner	workspace	Bitbucket Cloud removed support for a number of legacy terms and changed ownership relationships with workspaces becoming the key concept.
all	rowFilterByColumn, rowFilterRegex	select	These option values are no longer supported.
agile	id	board, sprint	The use of the id parameter for board and sprint ids has been replaced. Use the board or sprint parameters as they now accept either a name or an id. This reduces ambiguity.

Changed output formats

Clients	Action	Change	Reason

Clients	Action	Change	Reason
bitbucketcloud	various		Consistency across actions especially with the new workspace terminology.
jira	getUserList	key added to outputFormat 1	Consistency and importance of a unique key for Cloud.

Deprecated parameters

This is a notice that we have deprecated some other parameters so you can start migrating any scripts to the new support over time. It is likely these will be removed in a later version. This was part of an ongoing effort to simplify some usage scenarios and prune our interfaces to avoid confusion.

Clients	Deprecated	Replacement	Discussion

Clients	Deprecated	Replacement	Discussion
all	host	url	Specify host as part of the url parameter for database access.
all	port	url	Specify port as part of the url parameter for database access.
jira, confluence, bitbucket	targetPassword, targetToken, targetUser		Use targetServer referencing a ACLI configuration entry to specify this information.
bamboo	targetPassword, targetUser		targetUser and targetPassword were removed completely if favor of a ACLI configuration entry. Also, the Bitbucket server URL needs to be part of an application link defined between Bamboo and Bitbucket.

Removed environment variables

Environment Variable	First Deprecated	Replacement	Discussion

Environment Variable	First Deprecated	Replacement	Discussion
ATLASSIAN_CLI_PASSWORD, ATLASSIAN_CLI_TARGET_PASSWORD, ATLASSIAN_CLI_DB_PASSWORD	9.x	site configuration	Use site configuration to specify access parameters so they are not on the command line. Site configurations can reference any environment variable available. User who are concerned about securing their passwords especially on shared systems, should consider using secured variables available with 11.0.