We want to add some custom attributes to our ticket model automatically on several different zammad instance (prods, devs, test, etc), but I’m not sure the best way to go about.
The attributes are a handful of select, tree select, and text fields.
There seem to be 2 options:
Use the HTTP API
- Easy to code - we would just need to create the new attributes manually via the UI then introspect the JSON via the API and replay it against new instances
- Requires software external to Zammad that needs its own deployment and maintenance
- Unclear if it is possible to modify the attributes afterwards (add new choices for example)
- Limited functionality?
- Easy to deploy
- Raw power of rails
- It’s not clear how best to implement this, see below.
First, do the Zammad devs have a gut reaction as to which is the preferred choice?
Then, if taking approach #2, would the following procedure appropriate?