User provisioning: Group naming

[jazzlyn]

Hi guys,

currently I'm questioning the naming of our groups regarding Atlassian access. We are in the middle of the migration from Server to Cloud.

Our gsuite groups are named like:

name: team@xyz.com
email: team@xyz.com

Till now this was not related to Atlassian, we had separate groups configured in JIRA and Confluence server. With Atlassian access and the GSuite sync feature - although it is a bit limited - in general we wanted to use this for syncing our employees to Atlassian cloud.

Now the situation is that the group names are synced to Cloud and therefore we have group names like 'team@xyz.com'.

Addons like Timesheet reports & Gadgets already cannot handle this, see screen. It works when you initially create a report but it is broken, if you want to configure the existing report (update fields f.e.). Yes, maybe it is a bug and I should report it.

I'm interested in general, how you guys handle this. Is '@' in group names a no go? Did you encounter similar issues with other tools as well?

The problem with this is that it needs to be scalable, so the complete email seems like a good solution to me to create a unique identifier.

Why does this have a huge impact? Group names cannot be edited. So basically you have to delete and create a group if you want to change something. This will result in broken relations (filters f.e.).

Best, J.

[Marc - Devoteam]

Hi @jazzlyn

From my point of view using an email address as a group or even full name is usable. It might be considered bad practice.

Atlassian is not preventing the use of an '@' in a group name. The usage of a group with a '@' just works as a normal group without.

We use many app's (add-on's) and these groups are usable. 

It might be that the app (Timesheet reports & Gadgets) you are mentioning is not able to handle this. It would suggest that you raise an issue at their end, as Atlassian is not preventing the use.

Regards,

Marc

[Andriy Zhdanov]

Hi,

As developer of the plugin, I'd like to note, that report configuration page is generated by Jira, not by the plugin. Plugin only provides values, as follows:

public Map<String, String> getValues(Map params) {
  Collection<Group> groups = userManager.getAllGroups();
  Map<String, String> values = new TreeMap<String, String>();
  for (Group group : groups) {
    String groupName = group.getName();
    values.put(groupName, groupName);
  }
  return values;
}

So it's Jira (Atlassian) who converts values to email link, but I don't think they will change it.

Thank you.