[JRASERVER-28484] Improve handling of duplicate group - Create and track feature requests for Atlassian products.

Type: Bug
Resolution: Unresolved
Priority: Medium (View bug fix roadmap)
Fix Version/s: None
Affects Version/s: 5.0.6, 5.2.5
Component/s: User Management - Others
Labels:

Introduced in Version:
5
Support reference count:
11
Symptom Severity:
Severity 2 - Major
UIS:
3
Bug Fix Policy:
View Atlassian Server bug fix policy

We need to improve how we handle duplicate groups. Right now we just throw an error and fail. This results in support tickets. Instead we should have some kind of intuitive error thrown within the JIRA interface which offers a solution / workaround at the minimum. Ideally the logic would present the duplicate groups FQDNs and allow the user to pick which one they want to use.

2012-06-04 12:18:44,664 QuartzWorker-1 ERROR ServiceRunner     [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10200 ].
com.atlassian.crowd.exception.OperationFailedException: Unable to synchronise directory: duplicate groups with name 'IT'
        at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseMemberships(AbstractCacheRefresher.java:131)

is related to

JRASERVER-66599 LDAP group can't be added during login due to duplicate key row

Gathering Impact

relates to

JRASERVER-67942 Local groups should be applied globally over user directories

Gathering Interest

mentioned in: Page Loading...; Page Loading...; Wiki Page Loading...

Assignee:: Unassigned

Reporter:: Boris Berenberg (Inactive)

Affected customers:: 33 This affects my team

Watchers:: 19 Start watching this issue

Created:: 05/Jun/2012 4:40 PM

Updated:: 22/Apr/2025 2:14 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates