cheating using move issue, can fields be limited

[Tim Nixon]

We have some data in our issues we enforce in workflow transitions.

However, since most users have the desired ability to "Move" an issue to a different project it appears they can 'cheat' by moving to the same project and have edit for field values outside the usual transitions

Question is: on the "Move" screen(s) is there a way to make some fields read-only so they cannot be changed?

BYW they are not cheating the process, it's simply that our fear is that unknowingly they may change a field value breaking the process/reporting we use

[Jobin Kuruvilla [Adaptavist]]

Move issue should only prompt to edit "required" fields that are not already populated on the ticket. If you do not have required fields on the edit screen, you should be good.