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
| Client | Change | Replacement | Discussion |
|---|
Removed Actions
| Clients | Removed | Replacement | Discussion |
|---|
Removed Parameters
| Clients | Removed | Replacement | Discussion |
|---|---|---|---|
all clients except jsm | request | url | Affected action is renderRequest |
| bitbucket | sskKey | file |
Changed Output Formats
| Clients | Action | Change | Reason |
|---|
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.
| Clients | Deprecated | First Deprecated | Replacement | Discussion |
|---|---|---|---|---|
| jira | addFieldConfigurationScheme, addIssueTypeScreenScheme, addScreenScheme | 11.0 | createFieldConfigurationScheme, createIssueTypeScreenScheme, createScreenScheme | consistency across scheme actions |
| cli, csv, web | renderRequest | 11.0 | webRequest | |
| bitbucket | addBranch, removeBranch | 10.6 | createBranch, deleteBranch | consistency with bitbucketcloud client and general use verbage |
| jira | deleteComponent | 10.4 | removeComponent | consistency with addComponent |
| marketplace | getAppReviewList | 10.x | getReviewList | simplification |
| confluence | getPageHistoryList, removePageVersion | 10.x | getContentHistoryList, removeContentVersion | broader 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.
| Clients | Deprecated | First Deprecated | Replacement | Discussion |
|---|---|---|---|---|
| agile | id | 10.x | board | board parameter can be used for board name or id |
| jira | values, value2 | 10.x | field | field parameter can be used multiple times and includes field name and value |
| jsm | value1, value2 | 10.x | field | field parameter can be used multiple times and includes field name and value |
| jira, jsm | field2 | 10.x | field | field parameter can be used multiple times and includes field name and value |
| jsm | field1 | 10.x | field | field parameter can be used multiple times and includes field name and value |
| slack | autowait | 10.x | now automatically done | |
| all | host | 10.x | url | Specify host as part of the url parameter for database access. ACLI-2164 and ACLI-1897 |
| all | port | 10.x | url | Specify port as part of the url parameter for database access. ACLI-2164 and ACLI-1897 |
| jira, confluence, bitbucket | targetPassword, targetToken, targetUser | 10.x | Use targetServer referencing a ACLI configuration entry to specify this information. |
