Core workflows: Unable to submit tickets using custom object values after they are removed and re-added

[bahusafoo]

Infos:

• Used Zammad version: 6.0.0-1692790511.c8049cec.jammy
• Used Zammad installation type: package
• Operating system: Ubuntu 22.04
• Browser + version: Edge for Business 116.0.1938.54 (Official build) (64-bit), Opera, Firefox

Expected behavior:

• When clicking Create, a ticket should be submitted/created.

Actual behavior:

• A notice is displayed saying “Error ID XXXXXXX: Please contact your administrator.”:
  
  
• Looking in the production log, I see the following messages:
  
  

Steps to reproduce the behavior:

A simplified recreation of this:

1. add a text object “test input”
2. add a single select object “test selection” with values a b c d e f g
3. in core workflows make a priority 1 workflow that removes all those options from the obect
4. in another workflow priority 2 add b d f back to the object
5. add a priority 3 core workflow that displays “test input” if “test selection” is b or d and sets it as required.
6. As a test user (agent or customer, doesn’t matter), attempt to submit the ticket.

• I believe this is a continuation of GitHub Issue #4763 - I made a video outlining that original issue: https://www.youtube.com/watch?v=xGeXrh4_RZ8 - the UI display issue is resolved, but I am unable to submit any tickets that had their fields and readded now.

For me this is not working (tried as both customer and agent role) - I’m wondering if it’s working for @rolfschmidt? Apologies for bothering you again. So close to having what I need built out with Zammad, really appreciate the help/insight.

[bahusafoo]

I just did confirm, if I disable the first core workflow that removes the field options, this issue does not occur.

[rolfschmidt]

works for me, can’t reproduce with your steps

[bahusafoo]

So I’ve been trying to figure this out. In my first core workflow, I did not remove the “-” option originally when I removed the other select options. I have added that to be removed, and now I do not receive the error when submitting tickets. Does that help you have any clues of what would cause that error in the logs?