Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-3531

Recast alias change events as user renames for incremental Crowd-to-Crowd sync

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Obsolete
    • None
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      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.

      Attachments

        Issue Links

          relates to

          Suggestion - JRACLOUD-32200 Ability to detect a changed username in Crowd or "JIRA User Server"

          • Closed

          Suggestion - JRASERVER-32200 Ability to detect a changed username in Crowd or "JIRA User Server"

          • Closed

          Suggestion - CWD-3384 Detect user rename in Crowd-to-Crowd synchronisation

          • Closed

          Activity

            People

              Unassigned Unassigned
              dberrueta Diego Berrueta
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2m
                  2m
                  Remaining:
                  Remaining Estimate - 2m
                  2m
                  Logged:
                  Time Spent - Not Specified
                  Not Specified