...
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. As a related note, we now support multiple specifications for the findReplace and findReplaceRegex parameters and therefore are deprecating the older usage scenario of a comma separated list of colon separated pairs. This usage is still supported for compatibility at least for the near future, however, the legacy support only works if the action does not use the multiple support by using more than one of the parameters.
| 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. |
...