Release Notes 8.2

Created by Automation User
Last updated: Dec 03, 2020 by Former user (Deleted)Version comment

Overview

This page provides information about an individual release of the Atlassian Command Line Interface (CLI) family of add-ons.
More release notes for additional versions of this product are available on the Release Notes page.

Release Highlights

Release Date

2019-02-14

Version

8.2

Purpose
  • Jira, Agile, Service Desk, Tempo
    • Jira 8.0 support 
    • New quick filter actions for boards
  • Confluence
    • General improvements
  • Bitbucket
    • General improvements
  • Bamboo
    • Artifact handling improvements to improve use case coverage
    • Another createPlan option for handling replace use cases
    • More options for queueBuild and restartBuild 
    • More task alias support - JUNIT_PARSER, INJECT_VARIABLES, GINT3
  • Common
    • Internal changes to improve quality
    • Improvements to find and correct reference documentation errors
  • Fixes

Upward Compatibility Warning

  • Removal of obsolete support
    • Hipchat has been removed from the client distribution and Run apps. Atlassian has discontinued Hipchat in favor of their partnership with Slack.
    • The "all" client has been removed from the client distribution and Run apps. The capability has been superseded by extensive delegation support available for a number of releases that allows for creating multi-client scripts.
    • Run CLI for Bitbucket is no longer included in this release or future releases. 
  • BCLI-495 - Artifact name will no longer be added to the the directory location provided by user on getArtifact for a directory artifact. This may impact scripts using this action.

Compatibility


Compatibility

The Atlassian Command Line Interface (CLI) supports a large range of product releases. The matrix below provides compatibility guidelines based on testing, API compatibility information provided by Atlassian, and community feedback. User's are encourage to help improve compatibility information through discussions and issues. The CLI also works with releases not officially listed here since in many cases it uses remote APIs provided by Atlassian that have been stable for many years. Check previous versions of the CLI for coverage of earlier releases. Users should verify their usage scenarios on new releases. Support normally is limited to minimum releases indicated. Client requires at least Java 1.8. In some cases, new actions are only available on later versions of the server - these are often noted in the documentation or in error messages.

To simplify the matrix, we no longer list much older releases even though there is some level of compatibility for these as well. Refer to earlier compatibility notes for information on older releases.

See also Compatibility for overall information on supported Atlassian releases.

CLI Clients and Connectors

  • 8.2 clients require connectors at version 8.0 or higher. 
  • Cloud users usually need to update their clients regularly to address incompatibilities introduced by Atlassian with their daily Cloud updates. We deliver EAP releases to immediately cover any problems.
  • (info) While the Confluence CLI often works well on Confluence server releases prior to the ones officially supported, this may not be the case for some actions on version 6.x. If you are on Confluence release 5.9 or earlier, we recommend Release 6.4 or earlier.
  • (tick) 3rd-party Applications - like Tempo for instance: We don't explicitly list application versions, but normally test against a recent release of the application that is compatible with the platform it runs on.
  • (tick) Data Center is normally tested on the latest enterprise release designated by Atlassian.


Run CLI Add-ons

Add-ons install and run an Atlassian product server.

Atlassian Add-on Compatibility

The Atlassian CLI supports a number of different Atlassian add-ons like JIRA Software and Confluence Questions. We only test and support the most current maintenance release of the add-on available for the respective Atlassian application.

Atlassian Incompatibilities

The CLI clients always try to maintain upward compatibility between releases. However, in some cases this is not possible. Occasionally server differences may cause some compatibility issues.

Common

type key summary assignee reporter priority status resolution created updated due
Refresh

Run CLI Actions

type key summary assignee reporter priority status resolution created updated due
Refresh

JIRA and Agile CLI

type key summary assignee reporter priority status resolution created updated due
Refresh

Service Desk CLI

type key summary assignee reporter priority status resolution created updated due
Refresh

Tempo CLI

type key summary assignee reporter priority status resolution created updated due
Refresh

Confluence CLI

type key summary assignee reporter priority status resolution created updated due
Refresh

Bamboo CLI

type key summary assignee reporter priority status resolution created updated due
Refresh

Bitbucket and Bitbucket Cloud CLI

type key summary assignee reporter priority status resolution created updated due
Refresh

Slack CLI

key summary type created updated due assignee reporter priority status resolution
Refresh

Trello CLI

type key summary assignee reporter priority status resolution created updated due
Refresh

UPM CLI

type key summary assignee reporter priority status resolution created updated due
Refresh

CSV CLI

type key summary assignee reporter priority status resolution created updated due
Refresh