JIRA 3.0 Upgrade Notes
This page lists a few things to be aware of when upgrading from previous releases of JIRA to JIRA 3. To perform the actual upgrade, see the upgrade documentation.
Existing SMTP Mail Server 'From' address may break notifications (JRA-5089)
In JIRA 3, email notification 'From' addresses now contain the reporter name, eg. "Joe Bloggs (JIRA) <firstname.lastname@example.org>", where "email@example.com" is set by the admin as the SMTP mail server From address. If you have this address to already include a name (eg "Tech Support <firstname.lastname@example.org>", then email notifications will fail with errors like:
The fix is to edit
WEB-INF/classes/jira-application.properties, and change the following property value
jira.option.include.user.in.mail.from.address = true
- If using JIRA Standalone, the file is atlassian-jira/WEB-INF/classes/jira-application.properties, after which you should run bin/shutdown and bin/startup to restart.
- If using JIRA deployed as a webapp, copy webapp/WEB-INF/classes/jira-application.properties to edit-webapp/WEB-IFN/classes, make the change to the edit-webapp copy, run build to rebuild the webapp, and redeploy it on your app server.
Invalid characters break XML import
JIRA's recommended upgrade process involves deploying an XML backup of your data. Some users will find that the import fails with this error:
This is usually because the database contains control characters that cannot be
represented in Unicode, and hence XML.
The fix is to follow these instructions to remove the invalid characters from the XML before import.
Was this helpful?
Thanks for your feedback!