JIRA 4.0 : JIRA 3.0 Upgrade Notes
This page last changed on Sep 20, 2005 by jnolen.
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) <jira@company.com>", where "jira@company.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 <jira@company.com>", then email notifications will fail with errors like: 2005-01-06 11:30:53,856 ERROR [atlassian.mail.queue.MailQueueImpl] com.atlassian.mail.MailException: Sending failed; nested exception is: javax.mail.internet.AddressException: Missing '<' in string ``"Joe Bloggs (JIRA)" <Tech Support <jira@company.com>>'' at position 62 FixThe 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
Invalid characters break XML importJIRA'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 FixThe fix is to follow these instructions to remove the invalid characters from the XML before import. |
![]() |
Document generated by Confluence on Oct 06, 2009 00:28 |