bitbucketcloud

get and get list actions

Major interface and performance improvements. Default display output is now simple text output with selected columns deemed most likely to be wanted and quickly retrievable. Specify --outputFormat 1 to get previous default behavior with CSV output. Specific columns and outputType can be specified easily to customize view. Script writers are encouraged to specify exact columns needed for their script to isolate the scripts from changes and to optimize performance.

Easier to view data in text table format on reasonably sized terminal. New column selection capability makes easy to customize reports. Performance is much better if certain columns are avoided when they are not needed.

bitbucketcloud

getCommitList, runFromCommitList

getDeploymentList, runFromDeploymentList

getPipelineList, runFromPipelineList,

getCommit (only when using --commit @last and other filtering parameters)

getPipeline (only when using --pipeline @last and other filtering parameters)

Defaults to most recent items. Equivalent to setting the startDate parameter to -30d or @default.

Improve performance:
Commits, deployments, and pipelines are continuously being added and can easily grow to a large number of items. Unless a limit parameter is provided, the entire list might have to be evaluated to produce the desired list. Limiting by default prevents accidental long running requests. Use --startDate @all to avoid the default or specify a specific startDate based on your needs.

bitbucketcloud

getBranchList, getBranch (name search)

getPullRequest, getPullRequest (name search)

Defaults to most recent items. Equivalent to setting the startDate parameter to -365d or @default.

Similar to above.

bitbucketcloud

getPullRequestList column order

Having the author fields before the pull request field did not follow standards. Script writers are now encouraged with 12.0 to explicitly list the columns they need in the order they want in the columns parameter to best protect the script from future changes.

bitbucketcloud

getPullRequestList

The author columns were moved after the merge commit column on all output formats. Scripts can specify column order explicitly using the columns parameter to get previous behavior.

Design oversight not conforming to standards.

bitbucketcloud

getDownloadList

Date column renamed to Created

Clearer indication of what the column means. More consistent with other actions with a created column

bitbucketcloud

getBranchList

Target prefix removed from commit column headers and other column changes.

Consistency with other actions and avoid confusion.

bitbucketcloud

getUserList

User field no longer represents the deprecated Bitbucket cloud user name for older users. It is now consistently the nickname for all users.

Bitbucket deprecated the old usage for username even though it is still around for some compatibility things. It is confusing, so we settled on what Bitbucket recommends going forward.

jira

addFieldConfigurationScheme, addIssueTypeScreenScheme, addScreenScheme

11.0

createFieldConfigurationScheme, createIssueTypeScreenScheme, createScreenScheme

consistency across scheme actions

cli, csv, web

renderRequest

11.0

webRequest

bitbucketcloud

getSource

12.0

getFile

Both source and binary file data can be retrieved, so getFile is more appropriate terminology.

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