Jira 4.1.1 issue screen change

Hello,

We have recently upgraded from 4.0.1 to 4.1.1. However, We surprisingly came accross that the issue screen has been changed irreversibly. As we have searched in the forums, There is no backward compatibility. Since we are using Jira enterprise-wide, major changes affect employees. Upon this, we needed to downgrade. We have run this version for about 1 to 2 hours. There have been work of employees on the new version of jira. Even though we had backups of the old version, we did not want to lose the activities since the upgrade. However, it is not possible to downgrade with the database (data) of jira 4.1.1 to Jira 4.0.1. Because there is a version check. I have checked whether there is a major database structure change, fortunately, not. I edited the propertystring table to make db and application compitable with eachother. I eventually managed to run old version of jira with new version of db (without losing the works of employees).

I want to inform Atlassian that these kind of changes should not be made instantly. Now, we are in desicion not to use 4.1.1 for such a long time since the cost of coping with complaints is much more than compared to using old version. We try to look at major changes between versions, but we usually get lost on the documentation pages. We want to get informed kindly if there is any chance to use "old version" of issue screen with new version of jira 4.1.1. One further suggession, you should use warning mechanism, in previous versions, which informs customers that there will be changes in some of features in next releases. For example, you should be warning about the issue screen change starting from version 4.0. Again, you may offer that "Please use a test environment, install new version there, use it, like it, then upgrade". However, as I mentioned above by saying "irreversibly" , at least you should leave, as one of the forum commenters said, a legacy theme and let the customer decide whether to use new theme or not.