Please note that Jira2SVN 3.0 is incompatible with previous releases. Server, Subversion hooks and all clients must be upgraded at the same time.
Jira2SVN can now detect broken connections between a client and the server. When a connection breaks, both server and client will detect this independently and drop the connection cleanly. Connections can break for a variety of reasons. Common reasons are:-
In previous releases a broken connection could cause Subversion commits to hang (with one of the symptoms being a Subversion hook on the Subversion server being left behind). Such broken connections are now detected early and tidied up. Any hanging commits are terminated with an error message.
Minor release introducing support for access to JIRA server through HTTPS.
Release 2.1 is fully compatible with Jira2SVN 2.0. If upgrading to Jira2SVN 2.1 from 2.0, there is no particular need to upgrade clients and Subversion hooks as release 2.1 server is compatible with 2.0 clients and Subversion hooks.
You can now use Jira2SVN in environments where JIRA can only be accessed through the secure HTTPS protocol. You configure Jira2SVN to use HTTPS by specifying the protocol in the server config, e.g.:
jira_server=https://my.company.com:8080
The jira_server setting now allows http:// and https:// protocols for the Jira Server URL. If no protocol is specified, Jira2SVN will default to http://.
None.
Jira2SVN 2.0 is a major release, introducing a number of significant new features.
As a major release, Jira2SVN 2.0 is not compatible with clients, servers or hooks from previous Jira2SVN releases. Please make sure you upgrade all clients, servers and hooks to ensure a smooth operation.
Jira2SVN 2.0 provides a beta release of a Windows installer that makes installing the product easier, applying the most common settings. Please note that following installation some manual configuration may be required to customise Jira2SVN to match your needs.
With the 2.0 release it is now possible to provide Jira issue id's in the Subversion log message. This makes it possible to run Jira2SVN without any interaction without the Graphical User Interface (GUI).
It also makes it possible to use Jira2SVN without running a client. However, please note that some limitations apply. Please refer to the Jira2SVN Administration Guide for details.
You can now progress Jira tickets through the Jira workflow using Jira2SVN. Note that this is currently only possible through the Graphical User Interface and cannot be done via the new command line interface.
It is now possible for users to run multiple clients under the same user id. If you commit a change whilst running multiple clients, Jira2SVN will open the issue-selection dialogue window for all clients. Once you press Ok or Cancel on any of the clients, all selection windows open for the same user will be closed automatically.
It is now possible to display extra information from Jira issues in the selection GUI. Any Jira issue field, including standard and custom fields can be added to the list of fields displayed in the selection GUI.
If you do not supply a password in the Jira2SVN client configuration, Jira2SVN will prompt you for the password. With release 2.0, this password is now checked against the Jira server and immediate feedback is provided if the password is incorrect.
You can now configure Jira2SVN to add issue id's to the Subversion log message. The main purpose of this feature is to provide compatibility with Atlassian's FishEye.
Jira2SVN requires a custom field to be added in Jira for it to store Subversion information in Jira tickets. Jira normally displays the raw data of the custom field at the top when viewing a Jira issue. Since the information in the Jira2SVN custom field can get fairly large, a feature has been added to Jira2SVN that makes it possible to hide this information from view. Jira2SVN information is much more readable on the Jira2SVN tab.
Please refer the Jira2SVN Administration Guide for more details.
Jira2SVN hooks can now be run on virtually any platform using the Jira2SVN Portable Hooks. Please note that portable hooks have a number of pre-requisites regarding the availability of third-party software on your system, and you are therefore advised to only use portable hooks for platforms currently not supported with binary executables.
The layout of the information in the Jira2SVN tab has been improved for better readability.
Jira2SVN can now display Jira issue titles with any Unicode character set, allowing you to use scripts such as Chinese and Arabic as well as special characters in Jira issue titles.
Error reporting has been improved to provide more information if Jira issues cannot be updated or information cannot be retrieved from the Jira server.
An issue with the Jira2SVN licensing code and foreign language installations of Windows has been fixed.
The option allow_commit_without_change_id did not always produce expected results, and the behaviour has been improved.
This release adds the ability for users to avoid storing passwords in their client files. To use this, simply do not set a jira_password
in the client config file, and on startup, a password-prompt window will appear requesting the password instead.
This is the initial release.