-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DF default values do not work for article fields in masks based on ActionCommon. #2785
Comments
…ow default values to take effect.
…screens to enable usage of default values.
This bug also affects article dynamic fields in the FollowUp of CustomerTicketZoom. |
Maybe also relevant: In the comparable place for handling the dynamic field values, AgentTicketPhone makes use of default values stored in the user preferences: otobo/Kernel/Modules/AgentTicketPhone.pm Lines 705 to 713 in 8866f83
I didn't research this thoroughly, but at least AgentTicketActionCommon, CustomerTicketZoom and a few other masks do not use this UserPreference values. Perhaps this will be relevant if we re-introduce user-modifiable sysconfigs as referenced in #2539 (comment). |
…screens to enable usage of default values.
Closed with merging #2811 |
Add a multiselect field with default value to AgentTicketNote and see that it is rendered empty (if empty value is given).
The text was updated successfully, but these errors were encountered: