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

Incremental Crowd/Crowd synchronisation produces inconsistent events when a membership is deleted and recreated

      When Crowd processes synchronisation events to send to clients it omits membership deletion events if that membership still exists (on the assumption that it's a shadowed membership change). However, if that membership is now present because it was recreated since the deletion then Crowd will still send the recreation event, which will now fail as that membership was never deleted.

      Either the initial deletion should still be sent or the recreation should also be omitted.

            [CWD-3190] Incremental Crowd/Crowd synchronisation produces inconsistent events when a membership is deleted and recreated

            Atlassian Update - 9 April 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Crowd Data Center, please check our public roadmap.

            Kind regards,
            Crowd Data Center

            Ishwinder Kaur added a comment - Atlassian Update - 9 April 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments; this inactivity suggests a low impact. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Crowd Data Center, please check our public roadmap . Kind regards, Crowd Data Center

              Unassigned Unassigned
              jwalton joe
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: