Emily Riccardi

Hi! I'm stilling learning my way around this and trying to figure out the best combination of rules to ensure we're reviewing higher-priority articles more frequently while others are reviewed maybe once a year (and also not bombard my team and our stakeholders with notifications at once).

One thing I am noticing is when I set a filter and review the list of articles that fit that filter, it includes articles that have been archived. Is there no way to exclude these other than to fully delete them? Appreciate any advice!

My team is also seeing this on sporadic articles, I haven't yet figured out a pattern to the articles impacted. The published versions have content but the editor is suddenly blank. 

One difference from the original post though, I am not seeing the revision history change. The last change just shows as 'published.' 

Aha! Yes, and that links to this article, which I think would solve the need here: https://support.zendesk.com/hc/en-us/articles/4408832673818

Yeah, interesting this is reserved for Enterprise (we're currently on Guide Professional). Thanks for pointing me in the right direction!

Update: I think this feature for Guide Enterprise solves the need here, so updating the feature request to allow lower-level plans to do this. Seems like a pretty standard feature. (Thank you to Sam in the comments below for pointing this out to me!)

---

When we know an update to a product is coming that will impact an existing article, we'd like to be able to draft an update to that article and save it within Zendesk Guide before publishing that change.

Currently, if we need to draft an update to an already-published article, we have to do so in Google Docs and then copy/paste the changes into Guide when the product update is released. It would be easier to draft that update in Guide so when the update goes out, we can go in and click Publish.

For comparison, ScreenSteps does this -- you can have a published version, draft a change to that version and click 'Save as Draft,' which will add a 'Draft' flag/indicator on that article in the backend, but keep the previous version published. When the product change is released, we can quickly go in and click "Save and Publish" because the updated content is already there.