Make revisions have a 'track changes' feature, with ability to accept/reject changes | Feature requests

GatherContent

Create

Roadmap

Feature requests

Make revisions have a 'track changes' feature, with ability to accept/reject changes

Kayleigh Bates

February 6, 2019

Peta Levett

I'm using a trial version of the product, which I generally love - but not having this feature is making me think twice about whether we can get on board. I hope it's considered in the future!

Carys Daroy

Merged in a post:

Track Changes

Corey Colt

in line text reviews and showing updates made.

July 31, 2020

August 4, 2020

barbara aria

Yes! Currently when we have a project with multiple review/revise rounds we end up exporting to a trackable doc - so in the end the only value in GC is the ability to create and reuse templates across many complex items.

Chelsea Kimlel

The is the biggest improvement we need is to track, accept and reject changes and which user made them.

Kristel Miranda

It would be nice to include a feature that lets the user compare the document before and after editing.

Wes Miller

Yes! This would be very helpful to quickly see edits without going into revision history for cross comparison.

Lauren Stuart

This is currently the biggest improvement we need to be able to rely on GC for content creation. It comes up every single time I share my content for review.

Jessie Rogers

Our team will make many edits across our workflow status changes (we'll change an existing page then make more edits after reviewing with team. Then the copyeditor will make small changes and leave additional comments / suggestions). We need to know what has changed since the last published version, but there is no way to see those changes grouped together.

Adam Hawes

A way for writer to see what copy they are altering (in real-time) from the prior version as they work within the text. It also would provide us with an easy way to immediately denote what has changed in the copy from prior versions to current. This helps with internal reviews and can allow our downstream content administrators to easily decipher small content tweaks for what is live in production (making just the edits and not loading the entire page again).

Adam Hawes

I don't think 'track changes' needs to be a part of revisions as such. I think the execution needs to be more like GDocs or Word. So a mode where you make suggestions, which someone with the right permissions can accept or reject, with an audit trail of this (perhaps in revisions - ha ha!). This could be toggled on at a workflow level.

→