Pages up-versioned without edits

Question

Some of our pages are being up-versioned even though nobody has edited them. This is a bit of an issue for us as we use Confluence for our controlled documentation.

The issue seems to be caused by a change to the timestamp for Gliffy diagrams on the pages, however nobody has edited the Gliffys either.

Any ideas as to what could cause this?

Jan Revis · Answer

Hi Jake,

Thank you for your inquiry.  There are some scenarios under which Gliffy will up version your Confluence depending on whether you are in Confluence server or cloud.  However, I do not know of a situation where the timestamp field would be updated on its own.

The timestamp parameter is something specific to cloud so I assume you are in Confluence cloud.  The page update is a work around to a Confluence issue where a macro's properties are updated after the macro is initially created, causing the diagram to not render. The work around we applied updates the macro with the missing properties with a page update if missing parameters need to be applied.  That update should add additional properties besides the timestamp however.

The Atlassian issue is documented in https://jira.atlassian.com/browse/CONFCLOUD-62749.  It is marked as fixed, but when we last checked it is still not fixed.  The last comment from another vendor dated Oct 2, 2019 states it is not fixed.

Work Around

When you create a diagram, immediately it before making changes save the diagram, then reopen the diagram with a new editor session to continue working.  That should prevent the need to up version the document with the missing parameters

Actions

Contact Atlassian support to request that they reopen  https://jira.atlassian.com/browse/CONFCLOUD-62749

We will also follow up with Atlassian to make them aware that this is affecting users.

If this issue is resolved we will immediately remove the up version action.

Matt Reiner _K15t_ · Answer

Hmm, OK.

Friends from Gliffy, maybe you can chime in. :)

Jake Ward · Answer

Hi Matt, we are getting a new version in the page history. We're not using scroll verisons, just the out-of-the-box functionality