Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



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 (for 6.0 and above). 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

  • 7.x clients require connectors at version 7.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.


columnAttributesstyle=background-color: #F0F0F0;
Product, Releases, Tested releases
Confluence, "(/) 5.10, 6.0 - 6.6, Data Center, Cloud", "5.10.2, 6.5.0, 6.6.0, Data Center, Cloud"
JIRA, "(/) 7.2 - 7.7, Data Center, Cloud", "7.2.1, 7.5.0, 7.6.0, 7.7.0, Data Center, Cloud"
JIRA Service Desk, "(/) 3.2 - 3.10, Cloud", "3.2.0-051, 3.9.0--REL-0006, 3.10.0-REL-0005, Cloud"
Bamboo, "(/) 5.15, 6.0 - 6.3", "5.15.0, 6.2.1, 6.3.0"
Bitbucket, "(/) 4.6 - 4.14, 5.0 - 5.7, Data Center", "4.6.0, 5.5.0, 5.6.0"
HipChat, "(/) 2.2, Cloud", "Production upgrade channel: 2.2.4 (2017.04.24.053859), 2.2.5 (2017.08.01.224606), Cloud"
  • (info) While the Confluence CLI often works well on Confluence server releases prior to the ones officially support, this may not be the case for some actions on version 7.x. This is due to the removal of legacy SOAP support still available in 6.x versions (–options legacy). If you are on Confluence release 5.9 or earlier, we recommend Release 6.4 or earlier.

Run CLI Add-ons

Add-ons install and run an Atlassian product server.

columnAttributesstyle=background-color: #F0F0F0;
Add-on, Add-on installs on releases, Tested releases
[CCLI:], "Confluence 5.10, 6.0 - 6.6, Data Center", "5.10.2, 6.5.0, 6.6.0, Data Center"
[JCLIP:], "JIRA 7.2 - 7.67, Data Center", "7.2.1, 7.5.0, 7.6.0, 7.7.0, Data Center"
[BCLIP:], "Bamboo 5.15, 6.0 - 6.3", "5.15.0, 6.1.0, 6.2.1, 6.3.0"
[SCLIP:], "Bitbucket 4.6 - 4.14, 5.0 - 5.6", "4.6.0, 5.5.0, 5.6.0"

Version 7.0 - Removed Actions and Parameters

The CLI is using this version change to remove obsolete actions and parameters that have been deprecated for some time. This is done to simplify maintenance, improve performance, and allow for future improvements. These changes are being done now as a result of major advancements in JIRA and Confluence over the last couple of years:

  • JIRA 7.0 and the CLI migration to REST API from SOAP APIs completed a few years ago - see JIRA 7.0 Support Notice for differences between JIRA 6.x and JIRA 7.x.
  • Confluence cql and the CLI migration to REST APIs from SOAP APIs recently completed

Version 7.0 - Removed Actions and Parameters provides details on these changes. Automation scripts may need some minor updates to remove obsolete constructs.

Atlassian Add-on Compatibility

The Atlassian CLI supports a number of different Atlassian add-ons like JIRA Softwareand 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.