Version 7.0 - Removed Actions and Parameters

Description

With version 7.0 we are removing a number of previously deprecated actions and parameters. If you have older scripts, you may be impacted.

Actions

ClientActionReplacementReason
JIRAaddUserWithFile
  • Use runFromCsv together with addUser
  • runFromCsv is now the standard way of doing these types of actions
JIRAremoveUserWithFile
  • Use runFromCsv together with removeUser
  • runFromCsv is now the standard way of doing these types of actions
JIRAaddUserToGroupWithFile
  • Use runFromCsv together with addUserToGroup
JIRAremoveUserFromGroupWithFile
  • Use runFromCsv together with removeUserFromGroup
  • runFromCsv is now the standard way of doing these types of actions
JIRAlistUser
  • Use getUserList

JIRAupdateOrCreateIssue
  • Use createOrUpdateIssue
  • standard name for this type of action
ConfluenceaddUserWithFile
  • Use runFromCsv together with addUser
ConfluenceremoveUserWithFile
  • Use runFromCsv together with removeUser
  • runFromCsv is now the standard way of doing these types of actions
ConfluenceaddUserToGroupWithFile
  • Use runFromCsv together with addUserToGroup
  • runFromCsv is now the standard way of doing these types of actions
ConfluenceremoveUserFromGroupWithFile
  • Use runFromCsv together with removeUserFromGroup
  • runFromCsv is now the standard way of doing these types of actions
ConfluenceAll news actions
  • Use blog actions instead
  • Confluence terminology changed many releases ago back to blog
  • Examples: addBlog, removeBlog, ...
ConfluenceinstallPlugin
  • Use installAddon instead
  • Atlassian terminology change
ConfluencecheckPlugin
  • Use getAddon instead

Parameters

ClientParameterReplacementReason
JIRAasVersion
  • Automatically handled with the advent of JIRA 7.x and improved REST APIs to identify field types
JIRAasComponent
  • Automatically handled with the advent of JIRA 7.x and improved REST APIs to identify field types
JIRAasCascadeSelect
  • Automatically handled with the advent of JIRA 7.x and improved REST APIs to identify field types
JIRAlegacy
  • There is no legacy support available any longer
ConfluencereferencereferencePage
Confluencenews
  • Confluence no longer uses the term news in favor of blog
  • With cql support, blogs are identified by type blogpost
  • Specific blogs continue to be identified by year, month, and day parameters
Confluencepluginaddon
  • Atlassian terminology change
Confluencesearchcql
  • Legacy search has been removed in favor of the more powerful cql capabilities provided by Confluence
ConfluencesearchModifiedcql
  • Legacy search has been removed in favor of the more powerful cql capabilities provided by Confluence
ConfluencesearchTypescql
  • Legacy search has been removed in favor of the more powerful cql capabilities provided by Confluence
BamboosearchLabels
  • Use runFromBuildList together with removeLabels to replace use of searchLabels on removeLabels
Bambooattribute
  • Was being ignored
Allapi
  • This was used for very special cases and is no longer used as a way to customize API URLs for access as now multiple different access points may be used for requests
Allservice
  • This was used for very special cases and is no longer used. Primary use was for SOAP service customization.

Parameters - Use Changes

ClientParameterReplacementReason
ConfluencereferencereferencePage
  • only a change for movePage
  • reference parameter now has a different meaning across all clients