Release Notes 7.0

Created by Automation User
Last updated: Dec 03, 2020 by Vijay Ramamurthy - AppfireVersion 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 Date2017-09-08
Version

7.0

Purpose
  • New Tempo CLI client is now available in an extended Early Access Program
  • New Bitbucket Cloud CLI client is now available in an extended Early Access Program
  • Common
  • JIRA
    • Improvements to user management actions including standardization
    • Add group parameters to addUser
    • New shortcut actions
  • JIRA Service Desk
    • License model changes - now no charge with JIRA CLI license
  • Confluence
    • Improvements to user management actions including standardization
    • Improved publishPage support
    • Find/replace support on titles for copyPage and copySpace
    • Updated markdown support with new library
    • Add group parameters to addUser
    • Improved page permission support
    • New shortcut actions
  • Bamboo
    • New trigger and environment trigger actions
    • New runFromBuildList action
    • Export plan support for triggers
    • Other trigger related improvements
    • getEnvironmentList improvements
    • More support for continue protocol
  • UPM
    • Easy install of Marketplace add-on
  • Fixes

Additional Notes

JIRA 7.x only. Attempting to access JIRA 6.x servers will result in a error with CLI 6.0 and higher. Users needing JIRA 6.x compatibility should use Release 5.7.

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 (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

Cloud users may need to update their clients regularly to address incompatibilities introduced by Atlassian with their weekly update 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 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.
  • (info) Users needing JIRA 6.x compatibility should use Release 5.7.


Run CLI Add-ons

Add-ons install and run an Atlassian product server.

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 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

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

Run CLI Actions

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

JIRA CLI

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

Service Desk CLI

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

Confluence CLI

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

Bamboo CLI

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

BitBucket CLI

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

HipChat CLI

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

UPM CLI

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

CSV CLI

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

Tempo CLI

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Bitbucket Cloud CLI

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh