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

Loading


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

Loading


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
Support Request JCLI-617 Clone issue to another project failed Seungho Jung Bob Swift Major Triage
Bug CSOAP-296 "copyPageChildren" to same space does not seem to work Ionut Bob Swift Major Open
Bug CSOAP-299 problems importing Markdown URLs that include query parameters O'Shaughnessy Evans Bob Swift Blocker Reopened
Improvement JCLI-622 Need ability to share filters created by createFilter Richard, Woo Bob Swift Major Open
Support Request JCLI-619 copyFieldValue updating resolution field Chris Byrne Bob Swift Major Triage
Support Request CSOAP-384 "Scroll Translated" pages are not handled accordingly in the Confluence CLI copySpace command. Henrik Bach Bob Swift Critical Triage
Support Request JCLI-621 JIRA Command Line Interface (CLI) 3.4.0 intermittent error Sysadmins Fra Bob Swift Major Triage
Improvement CSOAP-205 CLI CopySpace does not preserve custom page order in space Stanislav Kalianov Bob Swift Critical Open
Support Request JCLI-605 Clone project not handling Epic links correctly Misho Ch Bob Swift Major Triage
Improvement CSOAP-377 remove space permissions for group that has been deleted Werner Dreier Bob Swift Major Open
Support Request JCLI-616 Jira CLI plugin not working because of Jira connector plugin dependency Sumedh Ganta Bob Swift Major Triage
Improvement JCLI-614 Specify HipChat room on create project Shannon Pence Bob Swift Major Open
Improvement JCLI-615 Clone issue should copy links to Confluence pages Bob Swift Bob Swift Major Open
Improvement BCLI-57 Replace legacy support with JSON and providing CSV list output Bob Swift Bob Swift Major Open
Improvement BCLI-45 Provide CSV output for getBuildList and similar Bob Swift Bob Swift Major Open
Improvement CSOAP-317 More Confluence Questions related actions Bob Swift Bob Swift Major Open
Improvement BCLI-61 Action to create deployment-releases Vinzenz Mennicke Bob Swift Major Open
New Feature BCLI-35 Add more deployment support Bob Swift Bob Swift Major Open
Improvement BCLI-36 Support cloning deployment projects and plans Bob Swift Bob Swift Major Open
Improvement JCLI-349 Copy other schemes with cloneProject Le Huu Tri Bob Swift Major Open
Showing 20 out of 208 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