On upgrade Installer detects modification detection to atlassian-jira. In JIRA Tomcat's configuration files such as server.xml are excluded from the check. Moreover, users are not provided with any warning or feedback from Installer requesting them to manually migrate any changes from used server.xml across to its equivalent in JIRA.

Significant number of our customers modify server.xml to provide HTTPS or AJP and some of them are likely to miss our warning in the upgrade guide. Therefore installer should help them avoid this 'simile' configuration problem in order to streamline their upgrade process.

Originally reported issue below:

Automated upgrade, when using the installer, erases SSL and IIS configurations

Hey guys,

So, on the new 4.4 JIRA, when you install it using the installer, you are promtped to upgrade an existing install. If this install is working already with SSL or IIS, after the upgrade is done, all these working confugurations stopped working.

So, steps to reproduce:

• make a JIRA pre 4.4 use SSL or IIS
• upgrade this existing install via Windows installer
• try to access JIRA

Any updates on this would be great!

Cheers

Thiago Prisco