Today we release JIRA Client 2.3.2, the next upgrade in the 2.3 series. This version adds support for JIRA 4.2 and fixes several problems present in previous versions.
Earlier versions of JIRA Client are not fully compatible with JIRA 4.2. Custom fields, labels, date and time fields may work improperly or not work at all. In JIRA Client 2.3.2 we have fixed all the discovered incompatibilities. If you're moving to the new JIRA version, please upgrade JIRA Client as well.
JIRA Client 2.3.1 added a different authentication method under the hood, and some customers have reported that it was unable to log in to their JIRAs. Version 2.3.2 takes care of the problem by trying the new method and reverting to the older authentication in case of a failure.
Additionally, we implemented a better support for CAPTCHA. In case JIRA asks for a CAPTCHA validation, JIRA Client will advise the user to log in using web browser and solve the CAPTCHA challenge. Then JIRA Client should be able to proceed and authenticate itself.
We have also fixed non-working Move Issue action and text searches, and a few other problems. Support for non-English JIRAs and the JIRA Order plugin has improved as well. Please see the change log for details.
Upgrade is recommended to all users. To upgrade from a previous version:
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.
ALM Works Team