Possible to change the Web Form based on previously given custom fields?

MrGeneration · August 17, 2020, 10:43am

Sorry, but at the moment Zammad doesn’t allow dynamic fields like you used to know them on OTRS.

We do have a enhancement issue for this which I believe does cover it:

github.com/zammad/zammad

objects for tickets should be dependent on group

opened 11:21AM - 17 Jul 17 UTC

closed 08:43AM - 25 Aug 21 UTC

gwingend

enhancement prioritised by payment core core workflows

### Infos: * Used Zammad version: 1.5 * Used Zammad installation source: (source, package, ...) * Operating system: * Browser + version: * 1076910 ### Expected behavior: It would be useful, if the additional objects you could create for tickets, would be dependent on the different groups in the system. So in example, if you have an object "asset number" this field should only be visible, when you create a ticket for group "hardware support". If you create a ticket for the group "user management" the object "personal id number" should be available, but not the "asset number" object. If the objects would be group dependent it would be possible to implement workflows with checkboxes for the agents that could be marked if the individuell task to close a specific ticket have been done. ### Actual behavior: A created object is visible independent of the selected group the ticket is created for.

It was also discussed here:

Before you ask: We do not have an ETA.