Problems with versioning

Comments

7 comments

  • Official comment
    Avatar
    Anshuman Dash

    Hi Mattias,

    Thank you for reaching out to us and sorry for the inconvenience caused.

    After going through your flow it seems to me that your conclusion may be right. There's a good chance it has to do with insufficient permissions.

    In order to investigate further could you please confirm the following - 

    1. Are there any restrictions set on the 'current' version of the document?
    2. Do you have the following permissions in the space you are creating the documents - Add/Delete Restrictions and Add Attachments?

     

    Best regards,

    Dash.

    Comment actions Permalink
  • Avatar
    Mattias Söderberg

    Hi Dash,

    As answer to your questions:

    1. I don’t think so. At least I have not set any particular restrictions.
    2. I asked our Admin to increase my permissions, which he did. This made it possible to add a version. Yay! However, I cannot edit the child pages in the document. I can edit the parent page, though. But I gave him the requirements you mentioned and let’s see if it works.

    I also got this question from our Confluence Admin: “When setting the permissions in Confluence, we found out that there is a new user called 'Scroll Documents for Confluence'. What permissions should this 'user' have?”

    Today it looks like this:

    As you see, I have the same permissions as the Admin. But it still doesn't work.

    Since some functions still doesn’t work, I would say that the “Restrictions” option should be green, both for me and for the “Scroll Documents for Confluence” user. Am I right?

    And since I'm not the Admin, is it OK to turn off the “Mail – Delete” and “Space – Export” options for me and the the “Scroll Documents for Confluence” user?

    Generally, should the “Scroll Documents for Confluence” user have the same right as the user that should administer the documents?

    Looking forward to your reply.

    BR/ Mattias

    0
    Comment actions Permalink
  • Avatar
    Anshuman Dash (Edited )

    Hi Mattias,

    Good to see that you are now able to save versions. But the error with the child page editing is highly unusual.

    In order to get to the bottom of this issue, could you please confirm the following - 

    • If you create a brand new document and save a new version, then are you able to edit the child pages?  

    Also, please find below the responses to the questions you have raised - 

    “When setting the permissions in Confluence, we found out that there is a new user called 'Scroll Documents for Confluence'. What permissions should this 'user' have?”

    The Scroll Documents for Confluence is necessary for  the migration of legacy documents (Documents created before July 2019).

    In case you do not have any such legacy documents, then you can safely revoke permissions for this app user.

    And since I'm not the Admin, is it OK to turn off the “Mail – Delete” and “Space – Export” options for me and the the “Scroll Documents for Confluence” user?

    Yes, that is correct.

    Best regards,

    Dash

    0
    Comment actions Permalink
  • Avatar
    Mattias Söderberg

    Hi Dash,

    I think that I've actually misunderstood the versioning feature a little bit. It seems as it is impossible to edit the content in a version in the page tree. Even when I created a brand new document and made some versions of it, I couldn't edit the child pages. Instead, I have to keep the original document (as a working version) and make all the editing in that document, then save a new version from the original document. Which, when I think about it, makes sense. One do not want to change an earlier version, instead one make a new version. So when this issue is cleared I think I can find a nice work flow.

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    Anshuman Dash

    Hi Mattias,

    It should be possible to edit content in a version in the page tree.

    A little digging revealed that the issue you are currently facing is something that other app developers and their customers have reported in the Atlassian developer community.

    Unfortunately, there is no solution that has been suggested in the thread yet. We are trying to get more information from Atlassian. But in the mean time I would encourage you to create a support ticket with Atlassian.

    We will also try to push this forward from our end, and will keep you posted if there is any development.

    On a different note, the workflow that you have mentioned in your last response is also what we recommend with Scroll Documents - work on the current version and save a new version (similar to a snapshot).

    Also, we are currently working on improving the versioning workflow in Scroll Documents. Would you be interested in participating in a user research and provide us feedback on some of the early concepts?

     

    Best regards,

    Dash. 

    0
    Comment actions Permalink
  • Avatar
    Mattias Söderberg

    Hi Dash,

    I would be more than happy to participate in the research. Just e-mail me the details.

    Meanwhile, I will check out the Atlassian community. I'm afraid that if I create a ticket there, the reply will be way too technicla for me. So I stick to the work-around for now.

    Have a nice weekend!

    0
    Comment actions Permalink
  • Avatar
    Anshuman Dash

    Hi Mattias,

    Thank you.

    My colleague will reach out to you with more information regarding the research.

    In the meantime, if you have any more questions regarding the app, please feel free to reach out to us at support@k15t.com

    Cheers!

    Dash.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk