Make the JIRA Configuration Tool's 'Save' button only save the configuration of the currently selected tab.

Make the JIRA Configuration Tool's 'Save' button only save the configuration of the currently-selected tab.

The JIRA Config Tool is a convenient, multi-purpose tool, which our various installation and upgrade procedures make extensive use of.

However, one annoying aspect of this tool is that clicking the 'Save' button saves all of its configurations (across all tabs, no matter what tab the 'Save' button is clicked on), including:

1. The location of the JIRA Home Directory (stored in the jira-application.properties file within the JIRA Installation Dierctory).
2. The database connection (stored in the dbconfig.xml file of the JIRA Home Directory).
3. The TCP ports that JIRA runs through (stored in the server.xml file within the JIRA Installation Dierctory).

When customers upgrade or install JIRA (using one of the manual upgrade/installation procedures), they can use this tool to perform the first two configurations above (the latter of which may require manual configuration of the dbconfig.xml file for specialised db setups). Manual configuration of the dbconfig.xml file might be required because those particular configurations are not supported by the JIRA Configuration Tool.

However, if the customer were to perform the JIRA Home Directory configuration step after defining a finely tuned DB connection (in a 'specialised' dbconfig.xml file which they manually configured), their specialised dbconfig.xml will be overwritten because the 'Save' button on the JIRA Configuration Tool saves the configs on all tabs - regardless of whether you like it or not. End result? They'll then lose their finely tuned configurations.

Hence, please make the 'Save' button only apply to the configuration tab its used on. Intuitively, many users would also expect the 'Save' button to behave this way - and it ultimately results in greater flexibility for them too.