only version page in space

Comments

9 comments

  • Avatar
    Amit Kapoor

    Ideally, you would version pages that change not on every day but for a specific version schedule - like product releases. MOM when versioned, you will be required to create a version for every date when you want it versioned for. It is not productive unless the entire space gets to use these versions in that manner. If I understand correctly, I would not version MOMs but add a date variable in the content and prefix/suffix the date in the MOM page title.

    0
    Comment actions Permalink
  • Avatar
    Roman Serazhiev

    Hi Stefan,

    versions created by Scroll Versions app are space-wide versions. The use case for using the app is geared towards technical documentation. Other use cases such as yours might not be easy to implement and follow with Versions.

    If you need versioning on a page level, why the built-in page revision history doesn't work for you?

    Roman.

    0
    Comment actions Permalink
  • Avatar
    Stefan Müller (Edited )
    If you need versioning on a page level, why the built-in page revision history doesn't work for you?

    as a page, what is a MoM in our case, shall be approved and released in a safe and reliable manner.

    0
    Comment actions Permalink
  • Avatar
    Roman Serazhiev

    Stefan,

    have you tried out Comala Workflows? You can use it to approve pages. If a page is edited after approval, it can be transitioned to a draft state automatically.

    Would this help you out?

    Roman.

    0
    Comment actions Permalink
  • Avatar
    Stefan Müller

    properly could as there is even a connector Comala <> Scroll but it isn't free, so it is not an option for the time being:(. 

    0
    Comment actions Permalink
  • Avatar
    Stefan Müller

    I'll try to put in other words

     

    I went through the documentation but still have difficulties to
    understand if our scenario can be feasible by it. I'm aware of the
    following Scroll Version Documentation
    <https://help.k15t.com/scroll-versions/latest/scroll-versions-documentation-110528202.html>
    entries:

    1. Roles and permissions
    <https://help.k15t.com/scroll-versions/latest/roles-and-permissions-153653325.html>
    2. Intro to Workflows
    <https://help.k15t.com/scroll-versions/latest/intro-to-workflows-153651322.html>
    3. Intro to Publishing
    <https://help.k15t.com/scroll-versions/latest/intro-to-publishing-150570014.html>
    4. How can I lock version editing after publish?
    <https://help.k15t.com/scroll-versions/latest/how-can-i-lock-version-editing-after-publish-110532097.html>
    5. Manage versions
    <https://help.k15t.com/scroll-versions/latest/manage-versions-153651332.html>
    6. Publish a Version
    <https://help.k15t.com/scroll-versions/latest/publish-a-version-110528291.html>
    7. and the before mentioned so-called Private Master Space
    <https://help.k15t.com/scroll-versions/latest/collaborative-editing-how-should-i-work-with-the-editor-s-draft-and-publish-functions-121930659.html>
    approach, where Work in one space and publish to another space,
    wherein you make us of the Confluence permission only.

    but as said before we have a frequent meeting with one of our key
    suppliers. For those purposes, we have a collaborative space in
    Confluence wherein we create and intend to archive our MoMs in the future.
    We would like to achieve, that during the creation of the MoM, it is
    only accessible to the smallest group (the attendees). During the review
    process, it shall be editable by some more people (e.g. those who got a
    task assigned to). After it was published it shall be accessible to
    anyone who has access to this space but in read-only.

    According to the above-referenced articles, our scenario must be somehow
    feasible but I miss some clear illustrations (pictures or may even
    videos) showing the setup process and giving us an impression how the
    space looks like during the process depending on the user's role. All
    that I can say that we would follow the Public Master Space approach.
    <https://www.k15t.com/blog/2013/12/best-practice-managing-versioned-documentation-in-confluence>Due
    to that limitation and the fact that I don't have the possibility to
    play around with Scroll Version I would highly appreciate if you could
    provide some screenshots.

    Moreover, there should be an option to easily access previously
    published version of an MoM (page) but as the version counter reflects
    the entire space an addition button/function would be necessary. Could
    that be done by Page Properties Macro
    <https://confluence.atlassian.com/doc/page-properties-macro-184550024.html>?

    0
    Comment actions Permalink
  • Avatar
    Roman Serazhiev

    Hi Stefan,

    I am sorry if I am not seeing the whole picture from your detailed description.

     

    In order to answer your questions, I would to understand exactly what you need and why. 

    We have a collaborative space in Confluence wherein we create and intend to archive our MoMs in the future
    Could you please explain what MoM stands for?

    The fact that I don't have the possibility to play around with Scroll Version
    Why don't you have the possibility to do so?

    There should be an option to easily access previously published version of an MoM (page) but as the version counter reflects the entire space an addition button/function would be necessary. Could that be done by Page Properties Macro?
    Would you like Page Properties Report to shot the page version? Or a control in the form of a button to select the page version?

     

    Roman.

    0
    Comment actions Permalink
  • Avatar
    K15t Team

    Hi Stefan,

    you have a very specialized and unusual use case and we will do out best to try and solve it. However the separation of the conversation across multiple channels only adds to the confusion and doesn't accelerate the process.

    For that reason I would like to ask you to only use the support ticket for communication to keep the whole truth in one place. I will have a look at all of the conversation so far and answer in the support ticket as well.

    Thanks you,

    Cheers,

    David

    0
    Comment actions Permalink
  • Avatar
    Stefan Müller
    1. Could you please explain what MoM stands for?
      Minuntes of Meetings
    2. Why don't you have the possibility to do so?
      Our productive system still runs with Confluence V6.5 what is too old for Scroll Version. The testing instance is supposed to be on a newer state but it hasn't been stable for a while and the admin is on vacation until the end of the month.
      I'm trying to get access to an Confluence Cloud demo through our Atlassian Partner but discussion has just started. I know that situation is more than only embarrassing and quite frustrating for the power user of us but that is how it is at the moment.

    3. Would you like Page Properties Report to shot the page version? Or a control in the form of a button to select the page version?
      Second would be excelent but we may couldgo with the first one

    --------

    1. For that reason I would like to ask you to only use the support ticket for communication to keep the whole truth in one place.
      will do, you are welcome

    Thanks for our interest in my challange!

    Stefan

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk