Skip to end of banner
Go to start of banner

Special Compatibility Notice for ACLI Version 11.x

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Work in progress

This page is incomplete and will be updated prior to final release of 11.0.

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 application releases and even to high degree across different environments (Cloud and Data Center). 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 11.x from 10.x or earlier. If upgrading from release prior to 10.x, see also Special Compatibility Notice for CLI Version 10.x.

Client Changes

ClientChangeReplacementDiscussion

Removed Actions

ClientsRemovedReplacementDiscussion

Removed Parameters

ClientsRemovedReplacementDiscussion
all clients except jsmrequesturlAffected action is renderRequest
bitbucketsskKeyfile

Changed Output Formats

ClientsActionChangeReason

Deprecated Actions

This is a notice that we have deprecated some actions 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. 

ClientsDeprecatedFirst DeprecatedReplacementDiscussion
jira

addFieldConfigurationScheme, addIssueTypeScreenScheme, addScreenScheme

11.0createFieldConfigurationScheme, createIssueTypeScreenScheme, createScreenSchemeconsistency across scheme actions
cli, csv, webrenderRequest11.0webRequest
bitbucketaddBranch, removeBranch10.6createBranch, deleteBranchconsistency with bitbucketcloud client and general use verbage
jiradeleteComponent10.4removeComponentconsistency with addComponent
marketplacegetAppReviewList10.xgetReviewListsimplification
confluencegetPageHistoryList, removePageVersion10.xgetContentHistoryList, removeContentVersionbroader support with the content action

Deprecated Parameters

This is a notice that we have deprecated some 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. 

ClientsDeprecatedFirst DeprecatedReplacementDiscussion
agileid10.xboardboard parameter can be used for board name or id
jiravalues, value210.xfieldfield parameter can be used multiple times and includes field name and value
jsmvalue1, value210.xfieldfield parameter can be used multiple times and includes field name and value
jira, jsmfield210.xfield

field parameter can be used multiple times and includes field name and value

 jsmfield110.xfieldfield parameter can be used multiple times and includes field name and value
slackautowait10.x
now automatically done
all

host

10.xurlSpecify host as part of the url parameter for database access. ACLI-2164 and ACLI-1897 
allport10.xurlSpecify port as part of the url parameter for database access. ACLI-2164 and ACLI-1897
jira, confluence, bitbuckettargetPassword, targetToken, targetUser10.x

Use targetServer referencing a ACLI configuration entry to specify this information.

Deprecated Environment Variables

  • No labels