Gerrit

I think that a warning popup is needed, before "agent" is automaticly checked. To prevent accidentily provide agent-permissions.

Now we switched to xlsx with Zammad 6.0, can we increase that limit?

> The **has changed** operator has a special functionality. It is only true for the moment when the owner has been set. It's use case is to e.g. prefill input...

I still do not understand, what the condition does, if he doesn't react to changed values. And why does it even make sense, to keep a condition, that reverts itself,...

I just understood and learned, that conditions are not working with all operators. Then maybe we need a warning, if a user choose a not working condition/oeprator-combination?

The order in browsing mode is defined by the user:   While the order of the search results should be "by last updated" (according to #5099). Or do I...

This might also be extended to conditional operators in Core Workflows and Trigger/Scheduler.

Custom BaseDN is (currently) only possible if the LDAP-server does not allow unauthorized connections. > Now, if your LDAP system restricts anonymous bind, Zammad 6.2 is equipped to identify this...

# Proposal GD 1 ``` contains one -> contains any one of contains all -> contains all of contains one not -> not containing any one of contains all not...

It is possible, but cumbersome. You can disable the "nodes" via Core Workflow with "remove option". But you would manually need to add all nodes that have leaves to that...