Skip to end of metadata
Go to start of metadata

26 Feb 2012

Summary

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.

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

3.1 - 3.5 and 4.0 - 4.1 (Note 1)

3.4.0, 3.5.13, 4.1.0
JIRA

4.0 - 4.4 (Note 2 and 3) and 5.0

4.3.3, 4.4.4, 5.0.0
Bamboo

3.2 - 3.4 (Note 4 and 5)

3.3.2, 3.4.0
Crucible

2.2 - 2.7

2.6.3, 2.7.10
Fisheye

2.2 - 2.7

2.6.3, 2.7.10

Notes

  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

Issues


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

Issues


Confluence Command Line Interface (CLI) Improvements

Issues

Loading
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

Loading
T Key Summary Reporter Assignee P Status
Improvement JCLI-721 Provide continue support on updateIssue and similar to ignore invalid fields Bob Swift Bob Swift Major In Progress
Support Request JCLI-718 CSV that worked in previous version now creates errors Emily Horton Bob Swift Major Triage
Improvement CSOAP-427 Add notify parameter to addUser and addUserWithFile Bob Swift Bob Swift Major Open
Support Request CSOAP-426 Issue authing via Confluence CLI Jim Cork Bob Swift Major Triage
New Feature JCLI-717 Avatar upload support Peter Hanraets Bob Swift Minor Open
Improvement JCLI-665 REST implementation of issue actions Bob Swift Bob Swift Major Quality Review
New Feature JCLI-365 Replace SOAP API with REST API use for JIRA 7 Bob Swift Bob Swift Major Quality Review
Improvement JCLI-705 Test and support JIRA 7.0 Bob Swift Bob Swift Major Quality Review
Support Request JCLI-709 Project is not valid James Somerville Bob Swift Major Triage
Support Request CCLI-83 How to use addgroup & AddUsertoGroup Cedric DEVAUX Bob Swift Minor Triage
Improvement JCLI-706 Add groups parameter to addUser Bob Swift Bob Swift Major Open
Improvement JCLI-694 project parameter should not be required for creating a subtask Bob Swift Bob Swift Major Open
Improvement BCLI-131 Ability to set specific plan permissions Rob White Bob Swift Major Open
Bug JCLI-702 Internal server error accessing projects with notification scheme NONE Bob Swift Bob Swift Major Open
Improvement CSOAP-424 Not able to copy User created templates saurabh sudhir Bob Swift Major Triage
Improvement BCLI-133 Add ability to order tasks ligup Bob Swift Major Open
Improvement JCLI-679 REST implementation of clone issue actions Bob Swift Bob Swift Major In Progress
Bug BCLI-132 Cannot delete a project with no plans Bob Swift Bob Swift Major Open
New Feature BCLI-120 Configure plan Branches information Luke Darnell Bob Swift Major Open
New Feature JCLI-688 support for sprints Wolfgang Fellner Bob Swift Major Open
Showing 20 out of 251 issues Refresh


Crowd temporarily discontinued

Crowd

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