The upgrade process should NOT add the Sprint field to all screens

Hi,

I read somewhere that Atlassian "argued" for this behavior "to make it easy for users to use this new functionality". I think that does NOT make any sense.
We have many (many!) different screens, after the upgrade, we had to go through ALL of them in order to clean all the mess up. Here some reasons why by default adding this field to ALL screens does not make any sense:

• you added the field for example also to screens used for Epics : a Sprint field does not have ANY sense for Epics. We have several other issue types where the sprint field does not have any sense !!!
• in our screens for Stories/Tasks/... we already had the field, but not in the first tab. The upgrade process added it again to the first tab , so the field is there twice now
• our screens are carefully designed, using different tabs where necessary. We try to avoid people have to scroll down, that the order of fields is "logical", ... . Just adding a Sprint field as last field on the screen does not help us a lot. Even for screens where the sprint field might be useful, we have to re-organize the field order and location. So your argument of "helping" the user does loose most of its value....

I would like to add : please Atlassian, DO NOT add fields to screens in an upgrade process anymore !!! In general, please DO NOT thouch the user configuration during an upgrade.

Cheers