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

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

XMLWordPrintable

      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 this will only affect Webkit based browsers, like Google Chrome and Safari.

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

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

            Ingrid Sluimer added a comment -

            Thank you, I will start watching CONF-39792.

            Ingrid Sluimer added a comment - Thank you, I will start watching CONF-39792 .

            Henrique Freitas (Inactive) added a comment -

            Hi ingrid.sluimer,

            The bug was reopened here: CONF-39792.
            Please take a look.

            Kind Regards,
            Henrique Freitas
            Cloud Support

            Henrique Freitas (Inactive) added a comment - Hi ingrid.sluimer , The bug was reopened here: CONF-39792 . Please take a look. Kind Regards, Henrique Freitas Cloud Support

            Ingrid Sluimer added a comment - - edited

            This issue is currently not resolved; we are experiencing this problem right now. Could it be reopened?
            We have Confluence Cloud as part of our JIRA Cloud instance. I believe the current version is 5.9.1.

            This seems indeed related to having whitespace in group-names, which I never would have figured out by myself, since all our groups have whitespace and this has never been different. After finding related issue CONF-38142 I ended up here. For a new Space, with permissions for only users (that contain whitespace) and a group (without whitespace), I CAN indeed save on Safari on MacOS.

            Related: https://answers.atlassian.com/questions/31682890/answers/32020556 (I will add another comment there with a link to this bug here).

            Ingrid Sluimer added a comment - - edited This issue is currently not resolved; we are experiencing this problem right now. Could it be reopened? We have Confluence Cloud as part of our JIRA Cloud instance. I believe the current version is 5.9.1. This seems indeed related to having whitespace in group-names, which I never would have figured out by myself, since all our groups have whitespace and this has never been different. After finding related issue CONF-38142 I ended up here. For a new Space, with permissions for only users (that contain whitespace) and a group (without whitespace), I CAN indeed save on Safari on MacOS. Related: https://answers.atlassian.com/questions/31682890/answers/32020556 (I will add another comment there with a link to this bug here).

            Jonathan Hult added a comment -

            I believe for a while this was working in our Cloud instance but is now broken again.

            Jonathan Hult added a comment - I believe for a while this was working in our Cloud instance but is now broken again.

            Stephen Sykes added a comment -

            So this got logged in July and is still impacting customers. This has wasted a fair bit of time (yep, we try and try and then open a support ticket , and then interact with the ticket - probably a dozen interruptions to workflow over a week, totaling well over an hour, plus the impact of interrupted workflow) and remains unresolved on the production public confluence cloud.

            Point being this should have been fixed quite some time ago.

            Stephen Sykes added a comment - So this got logged in July and is still impacting customers. This has wasted a fair bit of time (yep, we try and try and then open a support ticket , and then interact with the ticket - probably a dozen interruptions to workflow over a week, totaling well over an hour, plus the impact of interrupted workflow) and remains unresolved on the production public confluence cloud. Point being this should have been fixed quite some time ago.

            Jonathan Robidoux added a comment -

            Even if our Confluence version is newer than the fix (5.9.1-OD-2015.45.1-0006), we still have the same bug (can't change the permission from Chrome)

            The workaround is still working though (changing the permission from IE)

            Jonathan Robidoux added a comment - Even if our Confluence version is newer than the fix (5.9.1-OD-2015.45.1-0006), we still have the same bug (can't change the permission from Chrome) The workaround is still working though (changing the permission from IE)

            C added a comment -

            We are also having the problems with updating users. in addition to groups. is this issue being addressed as part of this defect?

            C added a comment - We are also having the problems with updating users. in addition to groups. is this issue being addressed as part of this defect?

            Peter Koczan (Inactive) added a comment -

            Hi Kelly,

            Apologies for that, I have not verified if it is available for download already or not, this is my mistake here. I cannot disclose an ETA on when it will be published, but rest assured it should not be too long from now, all the bugs/features intended to ship in this release are marked as Resolved in our public bugtracker: https://jira.atlassian.com/issues/?jql=project%20%3D%20CONF%20AND%20fixVersion%20%3D%205.8.7

            Peter

            Peter Koczan (Inactive) added a comment - Hi Kelly, Apologies for that, I have not verified if it is available for download already or not, this is my mistake here. I cannot disclose an ETA on when it will be published, but rest assured it should not be too long from now, all the bugs/features intended to ship in this release are marked as Resolved in our public bugtracker: https://jira.atlassian.com/issues/?jql=project%20%3D%20CONF%20AND%20fixVersion%20%3D%205.8.7 Peter

            Kelly Schoenhofen added a comment -

            People keep saying "was delivered" but I still do not show 5.8.7 as an available download; 5.8.6 is still the most current. Do we have an ETA?

            -Kelly Schoenhofen

            Kelly Schoenhofen added a comment - People keep saying "was delivered" but I still do not show 5.8.7 as an available download; 5.8.6 is still the most current. Do we have an ETA? -Kelly Schoenhofen

            Peter Koczan (Inactive) added a comment -

            Dear Consu,

            Using a different browser is only a workaround if you are affected by the problem. The bugfix was delivered in Confluence version 5.8.7, so upgrading to this release should solve the issue for you.

            Kind regards,

            Peter Koczan

            Peter Koczan (Inactive) added a comment - Dear Consu, Using a different browser is only a workaround if you are affected by the problem. The bugfix was delivered in Confluence version 5.8.7, so upgrading to this release should solve the issue for you. Kind regards, Peter Koczan

            Consu added a comment -

            SAying solved and the solution is: use another browser. Doesn't seem solved at all to me!

            Consu added a comment - SAying solved and the solution is: use another browser. Doesn't seem solved at all to me!

            MartiP added a comment -

            We recently upgraded to v5.8 and are having this issue as well. We're unable to assign permissions to individuals in Chrome. Firefox is our current workaround.

            MartiP added a comment - We recently upgraded to v5.8 and are having this issue as well. We're unable to assign permissions to individuals in Chrome. Firefox is our current workaround.

            Surya Sigdel added a comment -

            We installed 5.8.5 day before yesterday and are facing the same problem.

            Surya Sigdel added a comment - We installed 5.8.5 day before yesterday and are facing the same problem.

            Paul LaBarbera added a comment -

            We're also having this issue. Installed 5.8.5 last night.

            Paul LaBarbera added a comment - We're also having this issue. Installed 5.8.5 last night.

            Christian Baumann added a comment -

            Same behaviour for me in Google Chrome (Version 43.0.2357.124 m), but it´s working in Firefox (Version 31.4.0)

            Christian Baumann added a comment - Same behaviour for me in Google Chrome (Version 43.0.2357.124 m), but it´s working in Firefox (Version 31.4.0)

            Jonathan Hult added a comment -

            This affects us and was originally raised from our support ticket. It is not critical as there is a Firefox workaround. However, being fixed would be nice as then we don't have to worry about what browser is in use by space administrators.

            Jonathan Hult added a comment - This affects us and was originally raised from our support ticket. It is not critical as there is a Firefox workaround. However, being fixed would be nice as then we don't have to worry about what browser is in use by space administrators.

              hta Hieu Ta (Inactive)
              aborzzatto Andre Borzzatto
              Affected customers:
              24 This affects my team
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: