If JIRA is a tomcat/Java application, I don't understand why a complete reinstall, backup, and import would be needed when moving the application from one server to another server.
Why is is not possible to just copy all the files and clone the database? (of course, updating the database configuration and licenses on the new server)
Is JIRA designed to break if moved? This is not typical behavior for a JavaEE application.
Nope, it's not designed to break. But it often does because people miss things when they do a simple clone.
IF the operating system setup is the same on all the points that matter, you use the same directory structure, and you use the same database (or change the settings file to point to a new one), then yes, actually, you can just copy the whole lot. Although I'd tend to recommend skipping the index copy and rebuilding a new one.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events