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.7. Testing is done on Java 1.7. 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

Run CLI Add-ons

Add-ons install and run an Atlassian product server.

Notes

1. Tracked Atlassian issues references a few issues impacting Run CLI actions.

Atlassian Add-on Compatibility

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

• JIRA 6.4 EAP: JRA-41773 - Create project behavior has changed incompatibly. We have a workaround that is mostly compatible - JCLI-591 - Getting issue details... STATUS