Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-57554

duplicate item in dashboard all-updates after deleting a user

      Summary

      After deleting a user, it's observed that mentions contained in comments in the #all-updates view still exist with the original user name intact and there is an additional comment created that contains a key instead of the anonymised username:

      Steps to Reproduce

      1. Comment on a page and mention a user
      2. Delete that user
      3. Comment in Dashboard > All updates view contains user name and duplicate comment

      Context

      This bug only appears when the content in #all-updates belongs to the user being deleted. All-updates relies on change documents in lucene. As part of reindexing content with user mentions, we also reindex change documents, which involves first looking up the original change document for a given content object, deleting it, and then adding a new change document for the same content object. Unfortunately, looking up the original change document relies on the username. By the time, we try and look up the original change document, the user has already been renamed, so we don't find the original, but we do add a new one, resulting in duplication.

      See com.atlassian.confluence.search.lucene.tasks.AddChangeDocumentIndexTask#perform

      Workaround

      Perform a site reindex to remove the duplicates. Or, create more than 40 new changes, which will push the duplicate entry out of the all-updates tab.

        1. comment_mentions.png
          36 kB
          Will Masters

            [CONFSERVER-57554] duplicate item in dashboard all-updates after deleting a user

            Atlassian Update - 14 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 Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.

            Kind regards,
            Confluence Data Center

            George Varghese added a comment - Atlassian Update - 14 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 Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Confluence Data Center

              Unassigned Unassigned
              wmasters Will Masters
              Affected customers:
              5 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: