Uploaded image for project: 'Alfresco One Platform'
  1. Alfresco One Platform
  2. ACE-3811

Version number is not synced between on-premise and cloud

    Details

    • ACT Numbers:

      00329368, 00602325, 00681050 Premier

    • Epic Link:
    • Cloud or Enterprise:
      Cloud Only

      Description

      Description
      When we use cloud sync with on-premise and make a major version-up on synced contents, the synced side became minor-version-up instead of major-version-up.

      Steps to Reproduce
      1. Create folder in on-premise
      2. Configure folder to sync to a cloud location
      3. Upload test document to on-premise folder
      note: v1.0 is displayed for content version on-premise
      note: v1.0 is displayed for content version in cloud
      4. Click 'request sync' icon on-premise document
      note: v1.0 is displayed for content version on-premise
      note: v1.1 is displayed for content version in cloud
      5. Click 'request sync' icon on-premise document
      note: v1.0 is displayed for content version on-premise
      note: v1.2 is displayed for content version in cloud
      5. Use 'Upload New Version' action
      options for on-premise upload new version are minor 1.1, or major 2.0
      select major 2.0
      6. (DO NOT Click sync on doc on-premise) Refresh document page
      note: v2.0 is displayed for content version on-premise
      note: v1.3 is displayed for content version in cloud
      7. Click 'request sync' icon on-premise document
      note: v2.0 is displayed for content version on-premise
      note: v1.4 is displayed for content version in cloud
      8. Cloud, upload new version (options minor (1.5) or major (2.0)) select major
      note: v2.0 is displayed for content version on-premise
      note: v2.0 is displayed for content version in cloud
      9. On premise upload new version select major 3.0 or minor
      note: v3.0 (or 2.1) is displayed for content version on-premise
      note: v2.0 is displayed for content version in cloud
      10. On premise upload new version select minor
      note: v3.1 is displayed for content version on-premise
      note: v2.0 is displayed for content version in cloud

      Expected Results

      • on 'request sync' regardless of whether it is manually implemented or from action of upload new version (on either cloud side or on-premise side), the versioning history is consistent between on-premise and cloud to inlude versioning numbers (minor/major).

      Actual Results

      • on 'request sync' on premise, or upload new version the versioning between on-premise and cloud is not consistent nor does it act consistent.

      ex.

      • (initially) cloud version always increments a minor version, regardless of whether you upload a new version or you just simple click 'request sync' on the document
      • cloud version increments as a minor version, if you upload a new version on premise regardless of major/minor version select (until you have uploaded a major version on cloud side then versioning stops incrementing on cloud)
      • cloud version stops incrementing once you upload a new version via the cloud side, regardless of whether you upload a new version or you simply click 'request sync' on premise

      Basically, there is a number of combinations that seem to be of issue. Bottomline, versioning does not stay consistent between cloud and on-premise.

      Affected version: 39.2

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedissues Closed Issues
                  Reporter:
                  nkamada Nanako Kamada [X] (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel