Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for quite some time with very little progress being made. Rather than leave this issue here I'm going to close this out as won't fix. I believe this better reflects the status of the issue.

Regards
Steve Haffenden
Confluence Bugmaster

I've attempted to make everybody happy.

There are various other oddnesses that occur when groups or users have commas in the name, (eg a comma user's personal space gets a comma in the name even though spaces aren't allowed in space names). Therefore users and groups containing commas and backslashes have been disallowed.

However, since they may exist anyway due to LDAP or indeed old confluence instances, I have made both usernames and group names in text fields be escaped with backslashes.

IE a group named "the,\group" will be displayed in text fields as "the\,\\group".

This has been implemented in page permissions, global permissions and space permissions.

Unfortunately, commas are supported in LDAP, so we need to support commas in group names in the group picker. Users may not be able to change the LDAP groups which are assigned by their organisation.

I think the best solution is simply an escape character which escapes the commas. It shouldn't be necessary for the user to understand this, as long as the group picker popup inserts the escape characters when populating the text field as it closes.

Note that this problem affects global permissions and page restrictions as well, because they use the same group picker code.

We shouldn't allow commas in the group name. Otherwise we will run into troubles in all sorts of places.

A workaround for existing groups is to have a space instead of the comma when choosing the groups. This should also work as a separator.