Release Notes 5.1

On this page

Overview

This page provides information about an individual release of the Appfire Command Line Interface (CLI) family of add-ons.

More release notes for additional versions of this product are available here.

Release Highlights

 

Release Date

2015-12-22

Version5.1
Purpose
  • JIRA
    • Critical updates for JIRA Cloud users to cover REST API incompatibilities introduced in recent JIRA Cloud updates
    • Actions to easily delete unwanted screens, screen schemes, issue type screen schemes, and issue type schemes
      • Especially important on JIRA 7.x for user that create lots of projects
    • Clone issue fixes
  • Make exportSite work for JIRA and Confluence Cloud
  • Support latest Atlassian server releases
  • Fixes

Additional Notes

Important notice for JIRA Cloud users

Cloud users should upgrade their JIRA clients to 5.1 as soon as possible to avoid some issues related to incompatibilities rolled out to JIRA Cloud instance recently. Atlassian is aware of the issue and will try to prevent future occurrences.

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.7. Java 1.8 is highly recommended. Testing is done on Java 1.8 only. 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.

This release requires all Atlassian servers and client be running Java 1.7 or higher. Java 1.8 is highly recommended. See Compatibility for more information.

Java 1.8

Java 1.8 is strongly recommended for clients and will be required very soon! We no longer test on Java 1.7 and support may require Java 1.8. Oracle has ended public updates of Java 1.7.

CLI Clients and Connectors

(warning) - Limited support, no longer tested. Most actions should continue to work, but use with caution. Recommend upgrading.

(tick) - Supported releases.

 


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.

Common

type key summary reporter priority status
Loading...
Refresh

Run CLI Actions

type key summary reporter priority status fixversions
Loading...
Refresh

JIRA CLI

type key summary reporter priority status
Loading...
Refresh

Confluence CLI

type key summary reporter priority status
Loading...
Refresh

Bamboo CLI

type key summary reporter priority status
Loading...
Refresh

Bitbucket (Stash) CLI

type key summary reporter priority status
Loading...
Refresh

HipChat CLI

type key summary reporter priority status
Loading...
Refresh

Crucible and FishEye CLI

type key summary reporter priority status
Loading...
Refresh

 

Log a request with our support team.