Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-39701

Unable to save changes to Space Permissions for a group containing a whitespace

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Whenever a user tries to edit the Space Permission and update its information, Confluence fails to do so and report the following error:

      [Error] Error: Syntax error, unrecognized expression: [name=confluence_initial_viewspace_group_<instance_group>]
      

      It happens if the space has given a permission to a group which has a white space in the group name (i.e test group).

      Steps to reproduce

      1. Create a Space and create a group with a similar name.
        For example:
        • Space: Space test
        • Group: Space test
      1. Try to update the Space Permission by adding the Space test group.
      2. Hit Save All.

      Expected behaviour

      1. The permissions should be updated.

      Actual
      Nothing happens and all buttons are greyed out.
      The following error appears on the console:

      [Error] Error: Syntax error, unrecognized expression: [name=confluence_initial_viewspace_group_<instance_group>]
      

      Additional info
      Confirmed with Google Chrome and Safari.
      It doesn't happen when browsing with Firefox or Internet Explorer.

      Workaround
      Use other browsers, like Mozilla Firefox or Internet Explorer.

            [CONFSERVER-39701] Unable to save changes to Space Permissions for a group containing a whitespace

            We also have this problem in 7.4.11, not sure why it's marked as resolved.

            Daniel Köck added a comment - We also have this problem in 7.4.11, not sure why it's marked as resolved.

            This issue is still occurring in Confluence 6.2.0 (Server) with Chrome (Version 60.0.3112.90) so not sure why it is marked as "resolved".

            It appears that CONFSERVER-39701 and CONFCLOUD-39701 share the exact same comments so it's unclear if "resolved" would apply to both.

            All recent issues created referencing this problem have been marked as duplicate and redirected to this to track progress but there is not much public facing communication around the progress just a workaround and an incorrect status of "resolved".

            Given Chrome's prolific usage and our fairly recent version of both Chrome and Confluence, it's quite shocking to see this has been around for so long.

            IST Account added a comment - This issue is still occurring in Confluence 6.2.0 (Server) with Chrome (Version 60.0.3112.90) so not sure why it is marked as "resolved". It appears that CONFSERVER-39701 and CONFCLOUD-39701 share the exact same comments so it's unclear if "resolved" would apply to both. All recent issues created referencing this problem have been marked as duplicate and redirected to this to track progress but there is not much public facing communication around the progress just a workaround and an incorrect status of "resolved". Given Chrome's prolific usage and our fairly recent version of both Chrome and Confluence, it's quite shocking to see this has been around for so long.

            lho this issue is mentioned in release Confluence 6.0.0-OD-2015.48.0-0523 just promoted to jirastudio-dev

            Deleted Account (Inactive) added a comment - lho this issue is mentioned in release Confluence 6.0.0-OD-2015.48.0-0523 just promoted to jirastudio-dev

            lho this issue is mentioned in commits included in the Confluence 5.9.1-OD-2015.47.1-0002 release being approved for production: CPU-64

            Deleted Account (Inactive) added a comment - lho this issue is mentioned in commits included in the Confluence 5.9.1-OD-2015.47.1-0002 release being approved for production: CPU-64

            Adam Pryce added a comment -

            OD-47 is not found. Is it private or can you link us to it?

            Adam Pryce added a comment - OD-47 is not found. Is it private or can you link us to it?

            Minh Tran added a comment -

            Dear All,

            This ticket is still awaiting for deployment in OD-47. That is the reason why you do still not see the fix on your instance.
            Please follow this ticket for further information

            Best regards,
            Minh Tran
            Confluence BugMaster
            Atlassian

            Minh Tran added a comment - Dear All, This ticket is still awaiting for deployment in OD-47. That is the reason why you do still not see the fix on your instance. Please follow this ticket for further information Best regards, Minh Tran Confluence BugMaster Atlassian

            It affected Safari as well.

            Jeff McPherson added a comment - It affected Safari as well.

            Minh Tran added a comment -

            Hi rogier1 and All,

            This ticket has been fixed and are awaiting next Cloud deployment.

            Thanks,
            Minh Tran
            Confluence BugMaster
            Atlassian

            Minh Tran added a comment - Hi rogier1 and All, This ticket has been fixed and are awaiting next Cloud deployment. Thanks, Minh Tran Confluence BugMaster Atlassian

            I cannot imagine this workaround to be an acceptable fix for this ticket. Worldwide the usage of Chrome is 43% and is considered the most used browser, you cannot expect all these users to perform their permission management in a different browser.

            Rogier Kouwenhoven added a comment - I cannot imagine this workaround to be an acceptable fix for this ticket. Worldwide the usage of Chrome is 43% and is considered the most used browser, you cannot expect all these users to perform their permission management in a different browser.

            Since the original ticket was a major bug - would this likewise be a major issue?

            Ali Sajjadi added a comment - Since the original ticket was a major bug - would this likewise be a major issue?

              lho@atlassian.com Le Ho (Inactive)
              pjunior Paulo Junior (Inactive)
              Affected customers:
              8 This affects my team
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: