Joe Conti

Hi Katarzyna Karpinska -

I have been following this request for years (literally).  How did this go from the ability to COPY or DUPLICATE an article (the subject of this thread) to something you are calling "Article Multiplacement"?

These are two different use cases.  I don't see the ability to COPY/DUPLICATE an article on your roadmap - not under considering, not under planning.  

So I an just taking a wild guess here that it is not happening.

After a few years, I am going to "unfollow" the article because obviously Zendesk is not taking action on this.  Have fun recreating articles instead of duplicate/copy!!!!

If you go through the workflow as a Zendesk support admin and you want to create a Macro, you will see how convoluted the process is.

The other items still available on the left nav are limited utility when the most frequently used are now someplace else.

As a software development firm, we understand the challenge of juggling priorities.

In looking at this from the value versus level of effort perspective, where does Zendesk sit?

Is it not valuable enough to your users? Is it super complex and involved to copy/clone an article?

On the surface, it appears that this will help a number of your users and that it would be considered a low-to-medium level of development effort.

As a support manager, I'd like to be notified when any of my agents add an internal note to a ticket.  Typically the internal notes are questions about how to respond, how to solve the issue, etc.

Thanks!

Yes duplicating an article would be very helpful.