Uploaded image for project: 'Scroll Content Management'
  1. VSN-1859

Inconsistent behaviour when creating a remove change

    Details

    • Type: Feature Request
    • Status: Open
    • Resolution: Unresolved
    • Affects versions: None
    • Fix versions: None
    • Components: Scroll Versions
    • Labels:
      None
    • Sprint:

      Description

      When a remove change is created or an existing change is marked as removed, then the behaviour regarding retention of content (page content, attachments, labels) differs:

      If you remove a real change (i.e. a change that contains edited content and does not fallback to another change in the version history or an unversioned page), then all the content is retained in the change page - it is merely marked as a remove change and thus is unavailable. You can then come back any time in the future and decide not to remove the change, click edit and you will have exactly the same content as you had at the moment you removed the change.

      If you remove a change, that falls back to an unversioned page or to another change, an empty change page is created and marked as removed. If you continue to edit those fallbacks, then you will not be able to return to the removed change and continue your work from the same content.

      Thus the behaviour is inconsistent.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                christoffer Christoffer Bromberg [K15t]
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Backbone Issue Sync

                    Inspector Sketch