OnDemand Confluence - some users don't get indexed and are unsearchable, unmentionable and don't appear in a list of users.
Any clues?
So this is due to a known issue in Confluence, where sometimes a new user does not get added to the search index until you actually click on their profile in confluence.
Like so:
https://instance.atlassian.net/wiki/display/~user.name
After this, it'll get added to the index pretty much right away.
Hope this helps.
Ryan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same with me. I created this question before finding this post: https://answers.atlassian.com/questions/49691/at-mentions-not-working-in-comments-in-ondemand-confluence
The suggestion above to navigate to the user's space did not resolve this issue for us.
It had been working previously. Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I get the same issue on Confluence OnDemand (as of 15th April 2012)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is this issue still persisting? I took a look at the instance tied to your email address and it looks like all the users were showing up on the tests I ran. If the issue still exists, I'm wondering if it has to with the phonetic characters (I forget the proper name for them) not being indexed.
If the issue is persisting, please open a support ticket with the names of the users (so we don't post your account info here) and we can track down the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello and thanks for the reply,
seems to be OK now. We have applied the workaround described by Ryan Dunn in the ticket we raised:
Hi there,
This is due to a known issue where sometimes new users don't get added to the search index until you actually go to their profile (anyone).
He tried visiting one of the affected user's profile and then it started to work...
The rest seems to be also OK now.
Thanks for the effort!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.