-
Suggestion
-
Resolution: Obsolete
-
None
-
None
-
None
From the application point of view, the creation/removal/change of an alias is perceived as a user rename. Once Crowd-to-Crowd incremental sync supports user renames, there is no need to invalidate the incremental sync anymore on alias events, they can be rewritten as application-specific rename events.
- relates to
-
JRACLOUD-32200 Ability to detect a changed username in Crowd or "JIRA User Server"
- Closed
-
JRASERVER-32200 Ability to detect a changed username in Crowd or "JIRA User Server"
- Closed
-
CWD-3384 Detect user rename in Crowd-to-Crowd synchronisation
- Closed
[CWD-3531] Recast alias change events as user renames for incremental Crowd-to-Crowd sync
Workflow | Original: JAC Suggestion Workflow [ 3388387 ] | New: JAC Suggestion Workflow 3 [ 3630398 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1391927 ] | New: JAC Suggestion Workflow [ 3388387 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Resolution | New: Obsolete [ 11 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
New:
This issue relates to |
Workflow | Original: Crowd Development Workflow v2 [ 551616 ] | New: Simplified Crowd Development Workflow v2 [ 1391927 ] |
Remaining Estimate | New: 2m [ 120 ] | |
Original Estimate | New: 2m [ 120 ] |
Parent |
Original:
|
|
Issue Type | Original: Sub-task [ 6 ] | New: Improvement [ 4 ] |