Hope to get an answer.
I have a custom field of type date picker configured as required, I have added it to a transition screen.
In some cases this required field, have a value before I actually require it, via my transition screen.
What happens is that we in this situation needs to change to another date in order for jira to understand that this field has a value., otherwise the workflow does not let us transition the ticket.
Any idea on a workaround for this?
If a field is set as mandatory then it must have a value in order to create the issue in the first place.
If what you want is to assure any given field has a value at some particular point in your workflow what you must use is a validation in the appropriate transition.
I don't think there's a validation to check if the field value changes on transition but I guess you can resort to jira automation or some scripting tool in order to check this and in case it doesn't change then refuse the transition.
My interpretation here is that:
There are two potential causes here:
If it's the latter case, and the assumptions above are true (especially, you are not using any plugins), then you may have a case for Jira support. These issues are almost always due to plugins or automations having unexpected behaviours.
The workaround is simple. Stop the field from being required and either:
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events