Error message inconsistency when assigning space to guest user in confluence cloud

XMLWordPrintable

    • 5
    • Minor

      Problem

      When an administrator attempts to assign a space to a guest user who already has a space assigned, they encounter an erroneous and unclear error message:

      We ran into a problem saving the changes.
      

      Previously, the error message was specific and clear, stating:

      Failed to save permission for guest: guest already has access to another space.
      

      Environment

      Confluence Cloud

      Documentation:

      Steps to Reproduce

      1. Login to Confluence Cloud as an administrator.
      2. Navigate to the space permissions menu.
      3. Attempt to assign a space guest permissions to a guest user who already has another space assigned to them.

      Expected Results

      The expected result is that a clear and specific error message is displayed, informing the user that the assignment cannot be made because the guest user already has access to another space.

      Actual Results

      Instead of the expected result, a vague error message, "We ran into a problem saving the changes," is displayed.

      Workaround

      There is currently no workaround for this issue.

      Notes

      This issue appears to have occurred after recent updates were made to the space permissions screen (https://community.atlassian.com/t5/Confluence-Cloud-Admins-articles/New-Space-Permissions-Experience/ba-p/2580660). Although the correct error message is present in the request, the UI is not displaying it.

      This issue is causing confusion for administrators when assigning space to guest users, as the error message doesn't clearly explain what the problem is. A fix for this issue will improve user experience and minimize confusion when assigning spaces.

            Assignee:
            Matt Zuo
            Reporter:
            Edson B [Atlassian Support]
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: