Why is there an error with setting mandatory fields and manual transition at same time

The use case is that a customer has some custom fields on a request that need to be filled out before transitioning to the next phase.  These fields are not set at ticket creation and would need to be set afterwards.  Specifically, business rules were created that makes these fields mandatory when attempting to transition to that next phase (on enter of new phase).  This will prevent them from performing that manual transition unless they have provided values for those fields.  This works, if those fields are set and saved before performing the manual transition.  However, if you try and set those fields and perform that manual transition at the same time, you get an error message stating that the fields can not be null, as shown in the below screenshot.

Those fields would not appear to be null from the customer's perspective, since they did provide values for those fields, so why would they still get this error message?  A workaround could be to set and save those fields before transitioning the ticket to the next phase.  The question is why can't the mandatory fields be set at the same time as the manual phase transition?  I tried looking through existing ideas and discussions but didn't see anyone else asking about this.

Parents Reply Children
No Data