Ideas for Arc XP

As a creator, I want cloning links to persist when reverting revisions

Actual behavior / steps to reproduce:

  1. Create a story in Composer (revision 1)

  2. Clone the story using Composer

  3. Observe the cloned story is created with metadata linking back to the parent story

  4. Observe the original story has been updated with metadata linking it to the clone story (revision 2)

  5. Revert the original story back to revision 1

  6. Observe the link to the cloned story is lost

Expected behavior:
Following the revert, the original and cloned stories should remain linked.

  • Guest
  • Sep 16 2024
  • Will not implement
  • Attach files
  • Admin
    Mike Holland commented
    02 May 18:32

    Currently, the "link" between stories is metadata of a revision, so it is intended to be "lost" if you revert. Doing a "partial revert" is really a subjective decision.

    There has been a discussion about a more advanced DIFF tool for rollback where you could:
    1. Select From Version

    2 Select To Version


    Then you can see a list of fields that were changed from X to Y and select which ones you want in your new Draft version. This would be more appropriate since you are now authoring a revision with that content.