Skip to end of metadata
Go to start of metadata

26 Feb 2012


This release focused on expanding JIRA support, cross product improvements, and covering new product releases, especially JIRA 5.0. This is a simultaneous release of all CLI clients except for the Crowd CLI - see note. The Atlassian CLI distribution contains all CLI clients (except Crowd) plus the atlassian script and additional examples and help text shipped with the distribution.


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 in 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 Java 1.6 (recommended) or above. Testing is only done on Java 1.6. In some cases, new actions are only available on against later versions of the server - these are usually noted in the documentation.

Product Releases Tested releases

3.1 - 3.5 and 4.0 - 4.1 (Note 1)

3.4.0, 3.5.13, 4.1.0

4.0 - 4.4 (Note 2 and 3) and 5.0

4.3.3, 4.4.4, 5.0.0

3.2 - 3.4 (Note 4 and 5)

3.3.2, 3.4.0

2.2 - 2.7

2.6.3, 2.7.10

2.2 - 2.7

2.6.3, 2.7.10


  1. Confluence 4.1 introduced an incompatibility for adding comments - CONF-24194 (fixed in 4.1.3)
  2. Some of the newer JIRA CLI actions and other improvements are based on JIRA new REST apis. These APIs started being available with JIRA 4.2 and were significantly enhanced in JIRA 4.3 and later. Attempts to use these actions prior to the supporting JIRA release will result in appropriate error messages. Existing functions will still work on releases prior to 4.3, but releases earlier than 4.3 will no longer be automatically tested.
  3. JIRA 4.4 incompatibility bug regarding some custom field handling - see JRA-25034 and JRA-25732. JIRA 4.4.5 or higher is recommend if you plan to use JIRA 4.4.x
  4. Bamboo 3.3 or higher is required for action dealing with tasks
  5. Bamboo 3.4 is recommended for artifact handling due to BAM-9990

Highlights of Atlassian Command Line Interface (CLI) 2.5

JIRA Command Line Interface (CLI) Improvements

  1. runFromIssueList action - making it easier to run multiple operations based on a JQL query
  2. JIRA 5.0 support
  3. Labels field handling for JIRA 4.3 and above
  4. Time tracking fields
  5. Resolution field


Common Improvements

  1. Data from standard input for more actions
  2. --quite option available on more actions
  3. Improvements for the Run CLI Actions in Confluence add-on


Confluence Command Line Interface (CLI) Improvements


T Key Summary Reporter Assignee P Status
Bug CSOAP-120 Deleting News with removeContent yields java.lang.ClassCastException Lukas Karrer Bob Swift Major Closed

Run CLI Actions in Confluence add-on

More details are available on the add-on page - Run CLI Actions in Confluence

  1. Updated to 2.5.0 CLI level
  2. include-remote macro - beta

Release strategy

2.4.0 was the first release of this add-on. It is planned to concurrently release this add-on with each new release of the Atlassian CLI.

Open Issues

T Key Summary Reporter Assignee P Status
New Feature BCLI-120 Configure plan Branches information Luke Darnell Bob Swift Major Open
Improvement CCLI-89 Can run CLI create a JIRA issue and then launch it in a new window? Ethan Foulkes Bob Swift Major Open
Support Request JCLI-796 CopyIssues fail in the cloud James Burke Bob Swift Major Open
Bug JCLI-702 Internal server error accessing projects with notification scheme NONE Bob Swift Bob Swift Major Open
Improvement CCLI-90 Expose CLI replacement variables as page properties Bob Swift Bob Swift Major Open
Support Request CSOAP-450 findReplace not working Igor Mesonjnik Bob Swift Major Triage
Support Request JCLI-793 Multiple instances of CLI John Caron Bob Swift Major Triage
Bug JCLI-789 runFromIssueList and jql processed in random increments of 100 John Henne Bob Swift Major Open
Improvement JCLI-780 Need actions to delete custom screens and schemes Julian Flatt Bob Swift Critical Open
New Feature JCLI-790 Extend linkIssue action to support creating URL links Ethan Foulkes Bob Swift Major Open
New Feature JCLI-307 Ability to add/edit Remote Issue Links using the CLI interface Sven Kratzmeier Bob Swift Minor Open
Documentation improvement CCLI-85 Recipe for opening a Jira issue Ethan Foulkes Betsy Walker [Bob Swift Atlassian Add-ons] Major Open
Improvement JCLI-778 Add ability to activate or deactivate a user with updateUser action for Cloud Tony Sweeney Bob Swift Major Open
Improvement CSOAP-447 Add option to skip comments on exportSpace brian tagatz Bob Swift Major Open
Improvement JCLI-782 Allow changing filter ownership Gianni Pucciani Bob Swift Major Open
Improvement JCLI-622 Need ability to share filters created by createFilter Richard, Woo Bob Swift Major Open
New Feature JCLI-402 Create saved filters Shaun Dishman Bob Swift Minor Open
Support Request ACLI-247 ACLI: problem with base url using Kerberos authentication Piotr Kwiatkowski Pankaj Goel [Bob Swift Atlassian Add-ons] Critical Triage
Improvement BCLI-139 Need a stopBuild action Michael Stadelmeier Bob Swift Major Open
Improvement CSOAP-424 Not able to copy User created templates saurabh sudhir Bob Swift Major Open
Showing 20 out of 267 issues Refresh

Crowd temporarily discontinued


Crowd CLI removed from distribution

Crowd Command Line Interface (CLI) has been temporarily suspended from further development until the APIs are improved. As previously noted, Atlassian completely removed the Crowd remote APIs used for the CLI (sad) starting with Crowd 2.1. New replacement APIs do not cover most of the existing functionality. Atlassian is currently targeting application use cases and not automation capabilities for the Crowd APIs. It will be a while to sort out how the Crowd CLI moves forward, until then, the Crowd CLI has been removed from the distribution.

  • No labels