The full name and email address for a user in Confluence comes from the first enabled user directory with a user with that username. Other users with the matching username in other enabled user directories are shadowed. If two user directories are swapped, right now Confluence continues showing users in the people directory and mentions (and other user) autocomplete dialogs with the old full name, email and activation state. However, lookups that hit the database eventually find the correct full name, email and activation state.

      To fix this, Confluence should reindex all users that are shadowed between these two directories, when the user directory order changes.

      Similarly, Confluence should reindex all users when directories are enabled or disabled.

            [CONFSERVER-36277] Reordering directories does not reindex affected users

            Thank you for taking the time to raise, comment or vote on this Bug. We regret to inform you that due to a limited number of reports and based on our current backlog of higher impact issues that we are closing this issue as Timed Out.

            If this issue is still impacting you on a recent version please feel free to comment with the affected version. Any further details you may be able to provide regarding reproduction or impact of this issue may help us better address this issue.

            Thanks again.
            Cheers,

            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Thank you for taking the time to raise, comment or vote on this Bug. We regret to inform you that due to a limited number of reports and based on our current backlog of higher impact issues that we are closing this issue as Timed Out. If this issue is still impacting you on a recent version please feel free to comment with the affected version. Any further details you may be able to provide regarding reproduction or impact of this issue may help us better address this issue. Thanks again. Cheers, Confluence Product Management

              richatkins Richard Atkins
              richatkins Richard Atkins
              Affected customers:
              1 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: