-
Suggestion
-
Resolution: Won't Fix
-
3
-
When the following conditions are met, a group conflict will trigger.
- The provisioned group name matches an existing group with the same name on the target Atlassian site.
- The existing group contains a different set of members compared to the members in the provisioned group.
When a conflict occurs, the admins need to resolve them manually via the org administration (see document)
Suggestion : Allow an option to automatically override the groups in the Atlassian site with the provisioned group if there is a difference in group membership.
[ACCESS-1086] Ability to resolve duplicate groups conflicts from IdP automatically
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Labels | New: timeout-suggestion-bulk-close |
| Support reference count | New: 3 |
| Comment | [ A comment with security level 'atlassian-staff' was removed. ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 569963 ] |
| Description |
Original:
When provisioning group that has a name already existing in Atlassian cloud sites, the admins need to resolve the conflicts manually (see [document)|https://support.atlassian.com/provisioning-users/docs/resolve-group-conflicts-when-syncing-users/]
*Suggestion* : Allow an option to automatically override the groups on the site when the same group name exist on the provisioned data. |
New:
When the following conditions are met, a group conflict will trigger.
* The provisioned group name matches an existing group with the same name on the target Atlassian site. * The existing group contains a different set of members compared to the members in the provisioned group. When a conflict occurs, the admins need to resolve them manually via the org administration (see [document)|https://support.atlassian.com/provisioning-users/docs/resolve-group-conflicts-when-syncing-users/] *Suggestion* : Allow an option to automatically override the groups in the Atlassian site with the provisioned group if there is a difference in group membership. |
| Assignee | Original: ani [ ajagalpure ] | New: Vlad Svidersky [ vsvidersky ] |
| Description |
Original:
When provisioning group that has a name already existing in Atlassian cloud sites, the admins need to resolve the conflicts manually (see [document)|https://support.atlassian.com/provisioning-users/docs/resolve-group-conflicts-when-syncing-users/]
*Suggestion* : Allow an option to automatically override the groups on the site when the same group name exist on the provisioning data. |
New:
When provisioning group that has a name already existing in Atlassian cloud sites, the admins need to resolve the conflicts manually (see [document)|https://support.atlassian.com/provisioning-users/docs/resolve-group-conflicts-when-syncing-users/]
*Suggestion* : Allow an option to automatically override the groups on the site when the same group name exist on the provisioned data. |
| Description |
Original:
When merging groups from IDP to Atlassian, the duplicate group conflicts should be resolved automatically .
The requirement is similar to the feature which exists in DC version of Jira/ Confluence using delegated LDAP authentication . In DC, currently users can create shadow groups in Jira/ Confluence and AD groups are mapped to them automatically. |
New:
When provisioning group that has a name already existing in Atlassian cloud sites, the admins need to resolve the conflicts manually (see [document)|https://support.atlassian.com/provisioning-users/docs/resolve-group-conflicts-when-syncing-users/]
*Suggestion* : Allow an option to automatically override the groups on the site when the same group name exist on the provisioning data. |
| Remote Link | New: This issue links to "Page (Confluence)" [ 568659 ] |