Enhancement Request: Automate Backup and Restoration of Modified Files During Jira Data Center Upgrades

Problem

During the upgrade process of Jira Data Center, the system helpfully identifies a list of modified files that have been altered from the previous to the new installation. The current recommendation is to manually copy these files to a backup location before the upgrade and then manually restore some of those files (such as the JDBC driver) after the upgrade is completed. This manual step is prone to errors and can be time-consuming, especially for environments with extensive customizations.

Suggested Solution

I propose that the upgrade script be enhanced to automatically perform the following actions as part of the upgrade process:

1. Backup Phase: When the upgrade script identifies modified files that would not be automatically preserved through the upgrade, automatically copy these files to a temporary backup location. This step should occur before the upgrade process makes any changes to the Jira installation directory.

2. Restoration Phase: After the upgrade process has been completed and before the "start-up Jira" command is executed, automatically restore the backed-up files to their original locations. This would ensure that all custom configurations, drivers, and modifications are retained without manual intervention.

Why This Is Important

• Reduced Manual Effort: This change would streamline the upgrade process, making it more efficient and less labor-intensive for Jira administrators.
• Decreased Risk of Errors: Automating the backup and restoration of modified files would minimize the risk of files being accidentally omitted or incorrectly restored, leading to a smoother upgrade experience and less downtime.
• Improved Consistency: Ensuring that all environments maintain their custom configurations through upgrades would lead to more consistent and predictable behavior across different installations.

Workaround

Manually copy the files after the upgrade