ALM Works

Today we're glad to announce the release of JIRA Client 3.5, our desktop client for Atlassian JIRA. New JIRA Client is much faster, consumes less memory and includes a number of new features and improvements.

Core Improvement

This version marks the completion of transition to the newest JIRA's remote APIs and improvements to the internal networking functionality. We have completely stopped using old and slow JIRA's SOAP API — now JIRA Client uses only REST.

As a result, JIRA Client 3.5 downloads issues and metadata much faster, and consumes less memory during the network exchange. It can also handle larger local databases, up to 50 000 issues or more — the practical limit now depends on how many queries you have in the navigation tree.

Although initially planned as version 3.2, we feel that this improvement deserves something more than just a minor version number increase, so we tagged it version 3.5. (It's not 4.0 though, as there are not many new user-level features.)

New Features and Improvements

Besides being a faster and generally better product, JIRA Client 3.5 adds the following new functionality:

• Deleting attachments and comments.
• Customizable "Copy to Clipboard" action — please see the documentation about how to make Ctrl+Alt+C action copy to clipboard custom-formatted links to the selected issues.
• Careful handling of failed login attempts to avoid locking out users that have entered incorrect password.
• Restored support for connecting to Atlassian's jira.atlassian.com with the Atlassian ID.
• Limited support for custom fields coming from Tempo and JIRA Agile (GreenHopper) plugins.
• Automatic detection and switching to https-based JIRA address.

Upgrading JIRA Client

The upgrade is recommended for everyone who has a license with active maintenance and who's using JIRA 5.2—6.1 or later. If you have JIRA 5.0—5.1, then we advise to upgrade JIRA first, due to some limitations these versions have when providing remote access to JIRA Client. JIRA versions earlier than 5.0 are not supported.

This is a major upgrade, so please back your workspace before the upgrade. If possible, clear local database before running the new version.

After new JIRA Client has started, use menu Connection | Reload JIRA Configuration on every connection. Some of the new features might not be available until JIRA Client re-downloads issue information from JIRA.

Please let us know at support@almworks.com if you have any questions or need assistance.

--
Igor Sereda, Dmitry Peshehonov
ALM Works Team

• Download JIRA Client
• JIRA Client on the Atlassian Marketplace