...
| Clients | Removed | Replacement | Discussion |
|---|---|---|---|
| confluence | -t short flag for title | title | CLI standards are to use -t short flag for token, so Confluence needed to change to be consistent. |
| upm, confluence | addon | app | Atlassian terminology change from addon to app. |
| jira | board | agile client | With delegated support, there should be no impact as a jira request is automatically routed to the agile client |
servicedesk, bamboo | field3, field4, field5, field6, field7, field8 | field | The newer field parameter can be used multiple times and provides a better solution
|
servicedesk, bamboo | value3, value4, value5, value6, value7, value8 | field | The field parameter covers both field and value with a key = value syntax |
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 |
|---|---|---|---|
| jira | custom | field | It is a better practice to use multiple field parameters instead of a comma separated list and thus avoid quoting and delimiter complexities. |
| jira | field2,values, values2 | field | No longer needed with the use of multiple field parameters. |
| servicedesk | fields | field | It is a better practice to use multiple field parameters instead of a comma separated list and thus avoid quoting and delimiter complexities. |
| servicedesk | field1, field2, value1, value2 | field | No longer needed with the use of multiple field parameters. |
bamboo | fields | field | It is a better practice to use multiple field parameters instead of a comma separated list and thus avoid quoting and delimiter complexities. |
Start Scripts and Configuration
...