Title: Adding an answer history / version
-
What is your original issue/pain point you want to solve?
We have a lot of knowledge base articles (‘answers’ in Zammad terms) we want two add. Some of our customers are running an older version of our software and we would like to not have to add articles upon articles for each major version. -
Which are one or two concrete situations where this problem hurts the most?
-Different versions of our software and customers using our knowledge base.
-Adding a bunch of articles for each and every version -
Why is it not solvable with the Zammad standard?
This feature does not seem to exist (yet) -
What is your expectation/what do you want to achieve?
We want something like the following:
When you change or edit an article, to have a button that states something like “save / publish as new version” this will result in a version history for said article. The customer can then choose which version they want to read.
Your Zammad environment: latest version (demo)
- Average concurrent agent count: 10
- Average tickets a day: 15
- What roles/people are involved: Customers and Admins / Agents
Anything else which you think is useful to understand your use case: -