Cascading select custom field doesn't pop up in the "Move Issue" screen if the field has a context in source and destination projects.

We have two projects that share a common custom field (cascading select) between them. Each project has a distinct context for the field. When we move an issue from one project to another, the "Move Issues" screen doesn't pop up the shared field as one that needs to be updated as part of the move process. As a result, the moved issue now appears in the new project with an invalid, left over from the original project value. My users have to remember to go back and edit the moved issue after the fact to update the shared field's value to be valid in the new project.

For example,
Cascading SelectA
Context: Project A, All issues types
Options a-1, b-1, c-1

Context Project B, All issue types
Options: x-1, y-1, z-1

The cascading select field has different contexts for each project. The problem is that when I move an issue from Project A with a value of "a-1" to project B, it retains the value of "a-1" and I'm never prompted to map it to the values appropriate to project B.

This is a fairly serious problem because we define work queues in our different divisions based on this cascading select. If an issue is moved from one project to another with an invalid value in this custom field, it is, in effect, invisible to the folks in the destination and will languish.