ALM Works

Today we release JIRA Client 2.3.3, a patch that fixes a serious problem with JIRA 4.2 support discovered in the previous release. The problem can affect users who already had a connection to a JIRA 4.2 server when they upgraded from an earlier version of JIRA Client to version 2.3.2.

The symptom is that any synchronization attempt for a connection (loading a query, loading issue details, reloading JIRA configuration) just stalls at some point and never finishes. Sometimes this is preceded by an error report from JIRA Client. Connections to other JIRA versions, as well as new connections to JIRA 4.2, are not affected. After you upgrade to version 2.3.3, the broken connections will become functional again.

We have also fixed a minor problem with issue attachments that could disappear from view in certain rare circumstances. Please see the change log for details.

Upgrade is recommended if you use JIRA Client with a JIRA 4.2 server. To upgrade from a previous version:

1. Backup your workspace.
2. Install the new version over the old one.
3. Start JIRA Client and wait until background synchronization finishes.
4. If you are affected by the above problem, invoke Right-Click | Reload Query from Server on the most generic query that you are using.

This version may be used in a free 30-day trial mode or with any JIRA Client license key with active maintenance subscription. JIRA Client Lite may be used freely with any JIRA server running on a Starter license, or with a JIRA server that hosts a sponsored open-source project.

As always, we'd like to know your opinion. If you are experiencing a problem or need a feature, please raise an issue in our issue tracker.

Pavel Zvyagin
ALM Works Team

Links:

• Download JIRA Client
• Change log
• Forum
• Issue tracker