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.



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

JIRA 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 Confluence CLI plugin



Confluence 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

Confluence CLI Plugin

More details are available on the plugin page - CLI Plugin for 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 plugin. It is planned to concurrently release this plugin with each new release of the Atlassian CLI.

Open Issues

T Key Summary Reporter Assignee P Status
Support Request CSOAP-291 Cannot copy page and its subpages within the same space Epic River Bob Swift Major Triage
Improvement JCLI-470 Agile sprint actions Ulrik Schoth Bob Swift Major Open
Improvement JCLI-281 Not able to update WorkFlow Scheme with additional workflow Pranjal Shukla Bob Swift Major Open
Improvement CSOAP-289 Support space @all for runFromPageList Daniel Samuels Bob Swift Major Open
Support Request JCLI-503 Action file fails mysteriously Olav Cleemann Bob Swift Major Open
Improvement JCLI-502 Allow regex on getAttachmentList Bob Swift Bob Swift Major In Progress
Support Request JCLI-501 cannot create project michael b Bob Swift Major Triage
Improvement JCLI-492 JQL returning different results compared to navigator, need to convert search to REST David Gruber Bob Swift Critical Open
Bug CSOAP-286 copySpace requires replace parameter if home page not called Home. Bob Swift Bob Swift Major In Progress
New Feature BCLI-47 Provide new REST API endpoints Sunita Patro Bob Swift Major In Progress
Support Request CCLI-47 findReplace specify whether to be case sensitive or insensitive Mark Collett Bob Swift Major Triage
Support Request JCLI-498 JIRA CLI updateProject cannot find project key Steven Lam Bob Swift Major Triage
Improvement CSOAP-284 ability to disable users Michael S Simon Bob Swift Major Open
Improvement JCLI-496 ability to download complete list of users Michael S Simon Bob Swift Minor Open
Improvement CSOAP-243 copy page with CLI including scaffolding data Andrew van Ingen Bob Swift Major Open
Support Request BCLI-54 addRepository error for subversion Huseyin Demirel Bob Swift Blocker Triage
New Feature JCLI-495 API to Convert Sub-Task to Task Artem Belyasov Bob Swift Major Open
New Feature JCLI-365 Replace SOAP API with REST API use for JIRA 7 Bob Swift Bob Swift Major In Progress
Task JCLI-463 Test and support JIRA clustering Bob Swift Bob Swift Major In Progress
Support Request CSOAP-282 Cannot remove permission from a page Jason Friedman Bob Swift Major Triage
Showing 20 out of 174 issues Refresh

Crowd temporarily discontinued


Crowd CLI removed from distribution


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