最近搜索
没有最近搜索

Angela Werdenich
已加入2023年3月10日
·
最后活动2023年11月03日
关注
0
关注者
0
活动总数
16
投票
4
订阅
6
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Angela Werdenich
Angela Werdenich 进行了评论,
Katarzyna Karpinska Thanks for the suggestion. Is there any way we can bulk-change the author of all articles? We have some 40,000 articles in our knowledge base, so doing this manually for each article would be quite a pain...
查看评论 · 已于 2023年11月03日 编辑 · Angela Werdenich
0
关注者
0
投票
0
评论
Angela Werdenich 进行了评论,
I also want to support the call for this option - especially since we noticed that there is a major GDPR issue involved. The email notification contains the name of the author of the article which is not acceptable from a personal data protection perspective. So this means that we cannot use this important feature at all.
查看评论 · 已于 2023年10月19日 发布 · Angela Werdenich
0
关注者
1
投票
0
评论
Angela Werdenich 进行了评论,
This is probably our number 1 pain point working with Zendesk Guide, and we have addressed it several times (e.g. in https://support.zendesk.com/hc/en-us/requests/11328454), so we would highly appreciate it if you could prioritize it.
We would definitely prefer option 1 where multiple editors can work on an article at the same time, and see each other's changes in real time, without overwriting each other's updates when saving.
I really do think this would an extremely relevant feature which would benefit all users and allow Zendesk to evolve the product into a full content management system rather than a “ticketing plus” system.
However, option 2, technically blocking multiple people from editing an article at the same time, would already go a long way to avoid conflicts. For this, we have suggested one of the following 2 rules:
- preventing anyone other than the assignee from editing an article
- preventing anyone from editing an article if it is currently being edited by another editor
查看评论 · 已于 2023年4月12日 发布 · Angela Werdenich
0
关注者
0
投票
0
评论
Angela Werdenich 进行了评论,
Thanks Nicole, I posted it here: https://support.zendesk.com/hc/en-us/community/posts/5488958169754-Version-history-for-all-users
查看评论 · 已于 2023年3月13日 发布 · Angela Werdenich
0
关注者
0
投票
0
评论
Angela Werdenich 创建了一个帖子,
Hi Zendesk team,
Is there any chance we can enable the version history for all users (including light agents and end users)? This would be extremely important for us since we use Zendesk Guide for the complete documentation of our software solutions, and we have many articles that are updated on a regular basis (whenever there is an update in our software), so editors as well as our customers need to be able to quickly identify the changes between versions to understand what has been changed in the software.
Since this is so important, we currently use the following workaround:
- We manually mark all changes in another color than the rest of the page and use strike-through for deleted content (which is not even available in the editor so we have to do it in html).
- We include a summary of the main changes in a version overview at the top of each article.
- We download each article as PDF prior to publishing a new version and attach these previous version PDFs in the version overview.
This is extremely inefficient, time-consuming and error-prone and causes a lot of frustration among our editors and also customers when changes aren't properly marked.
Our requirement would be as follows:
- Enable Revision history for all users:
- Visibility of Revision history should be configurable/selectable in article settings (based on user types/segments)
- Restore previous version should only be possible for admins and agents
- Delete previous versions should be possible for admins and agents
- End-users should not be able to see names of authors in revision history.
已于 2023年3月13日 编辑 · Angela Werdenich
1
关注者
2
投票
0
评论
Angela Werdenich 进行了评论,
Hi Zendesk team,
Is there any chance we can enable the version history for all users (including light agents and end users)? This would be extremely important for us since we use Zendesk Guide for the complete documentation of our software solutions, and we have many articles that are updated on a regular basis (whenever there is an update in our software), so editors as well as our customers need to be able to quickly identify the changes between versions to understand what has been changed in the software.
Since this is so important, we currently use the following workaround:
- We manually mark all changes in another color than the rest of the page and use strike-through for deleted content (which is not even available in the editor so we have to do it in html).
- We include a summary of the main changes in a version overview at the top of each article.
- We download each article as PDF prior to publishing a new version and attach these previous version PDFs in the version overview.
This is extremely inefficient, time-consuming and error-prone and causes a lot of frustration among our editors and also customers when changes aren't properly marked.
查看评论 · 已于 2023年3月10日 发布 · Angela Werdenich
0
关注者
0
投票
0
评论