Move pages not showing proper error message on failure

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Low
    • Component/s: Organize - Move
    • None
    • Severity 3 - Minor

      Issue Summary

      When moving pages between spaces (single or bulk), if the target space already contains a (or more) page with the same title as page being moved the operation fails.

      On that failure, Confluence used to display error message "Content with these names already exist" (followed by the conflicting page title(s)), but now it displays a generic "We're having issues moving this content" message with no further information on the cause (or the actual conflicting titles), resulting in a bad user experience as it even suggests the users to try again.

      It seems the "proper error message" still appears in a very few cases, for example, when the actor is a Site Admin, but for most users the generic error is displayed.

      Steps to Reproduce

      1. Create a page "TestPage" in Space A.
      2. Create a page "TestPage" in Space B.
      3. Try to move "TestPage" from space A to B.
      4. Check error message

      Expected Results

      Error states clearly that operation cannot be completed because a page "TestPage" already exists in the target space.

      Actual Results

      "We're having issues moving this content" and suggests the user to try again or contact support.

      Workaround

      For the moment, there's no workaround for displaying the proper error message.

      If experiencing this error, please manually check for any pages matching titles between source and target space. Once identified, those pages can either be removed from selection or renamed (i.e. from TestPage to {}A_TestPage) to unblock the move operation between spaces.

              Assignee:
              Unassigned
              Reporter:
              Rodrigo Bozza (Atlassian)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: