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

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?

1 answer

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(.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,919 views 19 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you