refresh the “Estimated Close Date” and “Due Date” values when a JIRA Ticket is moved to different project

[Ramaiah Pendli]

refresh the “Estimated Close Date” and “Due Date” values when a JIRA Ticket is moved to different project,

when the issue moved to different project the field value should not be any date.

is there any way to customize move issue screen fields?

[GabrielleJ]

The JIRA "Move Issue" screen fields that are being shown during the operation are the fields required on the target project that should have a value (since the issue won't be created unless a value was specified). Even though you make both of the dates field required, you still must put a value on it when you move it to a different project.

Another option I can think of is to "copy" the current JIRA workflow that you are using and create a post-function in the "Create issue" event to clear the dates that you need. This way, the fields will always be blank during the initial status and you will just have to update these fields later on the project (during a transition or add it in the Edit Screen(.