"Currently Published" version doesn't seem to be right?

Comments

10 comments

  • Avatar
    Nils Bier

    Hi Jen,

    thanks for contacting us and sorry for the late reply, I wasn't in the office last week.

    The content of the currently published version will be the same when you publish version 1.4.

    We already have an improvement regarding the restriction of the currently published version: https://k15t.jira.com/browse/VSN-1334
    Please sign up at https://k15t.jira.com/secure/Signup!default.jspa to watch, to comment or to vote for this issue. The more votes an issue has, the more likely it is that it will implemented in one of the next releases.

    Editing the currently published version is not recommended, as the changes get overridden when publishing another version afterwards.

    Additionally you could have a look at the following page in our documentation: http://www.k15t.com/display/VSN/What+does+the+asterisk+*+in+the+Working+Version+dropdown+mean

    I hope that helps. Please let me know if you have any further questions.

    Cheers,
    Nils

  • Avatar
    Martin Kellner

    How can I preserve the changes in the current published version if someone changed this version?

  • Avatar
    Krohn, Matthias

    Hi Jen,

    you have to manually merge your changes from the currently published version to the "normal" version(s). That's the reason why it is not recommended to edit the currently published version.

    I recommend to edit the normal version and then re-publish this version so the currently published version is updated too.

    Regards,
    Matthias

  • Avatar
    Martin Kellner

    We used to publish in the same space. If you have more than a small group of users that can work on a space, you don't check each change on a page to be correct. The feature wish to protect the currently published version is on top of the voted issues. This gives me the hope that there will be a change in the near future. The only fix at the moment would be to publish to a different space.

  • Avatar
    Daniel Fitek

    Yeah VSN-1334 should clearly be addressed, but also the label "Currently Published" is extremely misleading.  It leads one to believe that it is simply a shortcut to editing the version that is currently published.  This is really bad usability.

  • Avatar
    Nils Bier

    Hi Daniel,

    thanks for the feedback.

    As we are aware of the misleading phrase "currently published" and the problems with editing this version, we'll most likely get rid of this version in the next major release of Scroll Versions.

    I saw that you've voted the issue, please feel free to also watch Scroll Versions in the Atlassian Marketplace (see https://www.k15t.com/pages/viewpage.action?pageId=82510672) to get a notification for every new release.

    Best,
    Nils

  • Avatar
    Martin Kellner

    In the sense of quality management editing a published version should not work at all. "Published" is an equivalent of "freezed" in this content. Changing content should always leads to a new version. If this becomes a minor or major version depends on the kind of change (typing error versus new or changed content).

  • Avatar
    Nils Bier

    Hi Martin,

    thanks for your feedback. We are currently working on the concepts for Scroll Versions 3.0, in which we plan to allow doc-admins to set restrictions on versions. Furthermore it will most likely - if we will not find any blockers during the conceptional work - be possible to "lock" the edit of published versions (by restrict the edit to an empty group).

    Best,
    Nils

  • Avatar
    Martin Kellner

    ... and integrate a function / option to save/move the currently published version - if it was edited - back to a page with a correct version designator. ;-)

  • Avatar
    Martin Kellner

    ... and integrate a function / option to save/move the currently published version - if it was edited - back to a page with a correct version designator. ;-)

Please sign in to leave a comment.

Powered by Zendesk