Fix the config script to update the dbconfig.xml file for the MS SQL database configuration to reflect the changes introduced with JIRA 7.5

Problem Definition

Since 7.5.x, JIRA is shipped with a new JDBC driver for Microsoft SQL Server.

Because of this change, the format of the file dbconfig.xml file needs to be changed manually if a customer upgrades JIRA from a version below 7.5 to 7.5 (for example, the prefix of the database URL is now 'jdbc:sqlserver://').

When the config.bat/config.sh script is run while using a dbconfig.xml file from an older version of JIRA, the script fails to run and gives the following error in the terminal:

Loading application properties from <JIRA_INSTALL>/WEB-INF/classes/jira-application.properties
Reading database configuration from <JIRA_HOME>/dbconfig.xml
No graphics display available; using console.
*** Unable to fully parse the current JDBC settings. Some settings may be blank.
*** Parse Exception: Unable to parse the JDBC URL 'jdbc:jtds:sqlserver:XXXXXXXXXXXXXX'. It should start with protocol prefix 'jdbc:sqlserver://'.

Why this is important

If the dbconfig.xml file is not properly configured, customers can't connect to the MS SQL database.
It can be problematic when a customer upgrades from a version below 7.5 to 7.5, since their dbconfig.xml file will have the old configuration.

Workaround

For now, there is a KB that explains how to update the dbconfig.xml file Updating JDBC URL for Microsoft SQL Server

Suggested Solution

It would be helpful if the config script could be fixed to automatically update the database URL from the dbconfig.xml (as well as any other change that should be made in this file), if the dbconfig.xml comes from a version before 7.5.x