Jira Issue Search Throws Error

[Phelan, Miranda]

We recently added a second user directory which syncs with a new company's active directory. Users are synced across ok. They can log into Jira and use the system fine.

However, several users have found the same issue: when searching in the issue navigator and creating a saved filter, when they try to add filters on certain fields (it seems they have access to choose Status but not all Types or Assignees) it throws the error "The Jira server could not be contacted. This may be a temporary glitch or the server may be down."

I found this article which seems very similar:

https://confluence.atlassian.com/jirakb/the-jira-server-could-not-be-contacted-this-may-be-a-temporary-glitch-or-the-server-may-be-down-1216973920.html

They created an har file for me. However, in the har file I don't see any of the errors mentioning QueryComponent! like it does in the article.

In the har file I do see an error saying "You are not authorised to perform this operation. Please log in."

Their permissions are the same as everyone else.

They tried different browsers and they see the same error in Chrome and Firefox.

Not sure what is causing this error. Any ideas? thx

[Mirek]

Hi @Phelan, Miranda 

The error "The Jira server could not be contacted. This may be a temporary glitch or the server may be down" might be related to many things not only to QueryComponent ..

Many times problems are on an network error (firewall or something like that).. but not always

https://confluence.atlassian.com/jirakb/the-jira-server-could-not-be-contacted-this-may-be-a-temporary-glitch-or-the-server-may-be-down-300814851.html

this example is showing that is might be not related to JQL but a plugin.. so there might be more likt it is described in KB it could be

• Cookies, Browser history, or Corrupt Cache
• Network issues on the machine
• Browser Extensions
• The browser is running a deprecated version

But those are only most common things..

The reason that you synced with corporate AD I do no think have any relation. This error mostly mean some problem between client and a server or the client itself so that is why it is good to verify the HAR (or developers tools for any issues. 

If you do not see any error in the HAR that might require more effort to troubleshoot.. So in that case try to figure out what connects all of those users that have problem (since I guess you are not able to reproduce this problem, right?)

This mean that there might be some correlation (maybe they are from one single location using the same network?) . Do you see any?