JIRA 4.4.1 Upgrade Notes

Upgrading from JIRA 4.4 to 4.4.1

Please follow the instructions in the general upgrading JIRA documentation.

Changes to the CSV Importer

Customers using the CSV importer feature and JIRA's Jelly Tags should be aware that the CSVReader class is now based on au.com.bytecode.opencsv.CSVReader rather than com.mindprod.csv.CSVReader. As a result of this change, the backslash character ('\') is now handled differently. If the backslash is found inside quoted text it will be ignored (removed) unless it precedes another backslash or a double quote. In case it does the following character will be kept but the first backslash will be omitted. See JRA-25315 and JIM-596 for details.

Fixes to SOAP and XML/RPC compatability

In JIRA 4.4 there was an accidental break compatibility of the SOAP and XML/RPC apis. Basically "Select" and "Multi-Select" custom fields were sending and expecting option ids instead of data values. This has been corrected and the SOAP and  XML/APIs should now behave as they did for JIRA 4.3 and earlier. This is fully documented in issue JRA-25374. If you made changes to handle this compatibility breakage, you may need to revert your changes.

Changes to the default value of the jira.search.views.max.limit property

The jira.search.views.max.limit property sets a 'hard' limit on the number of issues returned. See Limiting the number of issues returned from a search view such as an RSS feed for details.

In JIRA 4.4.0, this value was disabled by default, by being either absent from the jira-config.properties file or present in this file but disabled with a preceding '#'. From JIRA 4.4.1, however, this property has a default value of 1000. See JRA-25298 for details about why this changed.

Upgrading from JIRA 4.3.x and earlier

In addition to the above, please read the JIRA 4.4 Upgrade Notes and as well as the Important Version-Specific Upgrade Notes for the versions of JIRA you are skipping.