Conditions and actions allow to set ineligible users as owners or customers

[MrGeneration]

Infos:

• Used Zammad version: develop / 5.3
• Installation method (source, package, ..): any
• Operating system: any
• Database + version: any
• Elasticsearch version: any
• Browser + version: latest Firefox (Windows)

Expected behavior:

When modifying an object with conditions or actions, Zammad will verify if customer and owner users are eligible for corresponding fields.

Actual behavior:

When modifying an object with conditions or actions, Zammad allows to set any user as owner or customer. This allows to create a configuration that may not work as expected.

For example, when adding a ticket template, Zammad allows to set any user from the database as an owner. When applying this template to a ticket, Zammad tries to set the user as owner and will fall back to "-" if the affected user is not supported in that scope.

This issue applies to :perform, :conditions, :options attributes in Job, Macro, Overview, Sla, Template, Trigger classes.

Steps to reproduce the behavior:

• try to add any customer user as owner of a template and then apply it in a new ticket

Yes I'm sure this is a bug and no feature request or a general question.

[dominikklein]

I think this related to the problem that the owner field in general shows currently in the complete admin area the wrong values (same like the customer field).