Move Issue: Update Fields

[chintu Parameshwar]

Hi,

I'm moving an issue from Project A to Project B. The problem is, in step3("Update fields"), I have seen many custom fields that are not on project B's target issue type edit/view screens. If I give a value to any of the field, its not displayed on edit/view screens of the newly created(target) issue. But it has a value in database.

The Jira documentation says:

Custom Fields — If you have defined required custom fields for your issue, which do not exist in your target project, you must set values for them. You will only be prompted to change the enter values for required custom fields in the target project, that are missing values. If you wish to change the existing values for other fields on your issue, you can do this after the move is complete

But I'm able to see most of non-required customfields and non-existant(on defined screens) fields. FYI, These custom fields exists in Field Configuration, but not on the target issue type screens.

Could you please let me know how I can get rid of all these fields from move operation.

Thanks in advance!

[Dieter · Accepted solution]

Did you already make sure there isn't any field configuration context defined for the target project for the obsolete fields? It's hard for me to imagine that the move could ask for custom field values if the custom field is not relevant for the target project. Maybe your fields are global? Try to define field configuration contexts which include just the source project and let us know how it goes

[chintu Parameshwar]

Thanks Greiner! Yes, your right, those fields are global and their context is for all the issue types. I have modified the context. It's working fine now. Thanks again.

[Dieter]

glad i could help :-)

So a little vote would also be nice for me ... ;-)