JQL box is not displaying .

[Megha Dutta]

we are using jira version 7.12, when i check saved filters JQL box is not displaying there and export and Tools option is also not active on that page.

[Olga Videc]

Hello @Megha Dutta 

The same issue reported and resolving in

 https://community.atlassian.com/t5/Jira-questions/Advanced-search-does-not-display/qaq-p/660321

You can click watch on an issue to see the development

BR, Olga

[Megha Dutta]

Still the problem is same in firefox

[Megha Dutta]

Hello Olga,

I tried the same at firefox but the same result m getting jql box is not displaying in saved filter nor I found any option to edit already saved filter's jql. Kindly help.

[Megha Dutta]

.

[Olga Videc]

Hello @Megha Dutta 

Are you part of the Admin group, do you have administration permissions? 

Global permissions could be the problem, you need to go to:

Admin console ->System -> find Global permissions and grant your self or your group permission to bulk edit and Manage Group filter

But I think you don't have admin access, therefore, you need to contact your administrator to grant you that access.

Just press cog(right top corner next to your user) and you should see Jira administration if you don't have admin access.

https://confluence.atlassian.com/adminjiraserver073/managing-global-permissions-861253290.html

BR, Olga

[Megha Dutta]

Hi Olga,

I have admin rights and manage group filter rights but still facing same issue.

[Olga Videc]

Hello @Megha Dutta 

Can you please send me a screenshot?

Thanks, 

BR, Olga

[Megha Dutta]

[Megha Dutta]

Hello Olga,

Pls find the above screens as required by you.

And one more issue we are facing since yesterday one bulk task Id is stuck we re-indexing, post man and curl command but still issue persist . Kindly guide.

[Olga Videc]

Hello @Megha Dutta 

Bulk edit global permission

Are you part of the BULK EDIT group? Because this group has permission to bulk edit.

Second, missing search box

You have re-indexed your Jira?

Who monitors your instance? Is your database healthy, what was the last time you updated Jira?

IS your VM "strong" enough to support your Jira instance? Check your VM resources.

Your sysadmin should know this info.

BR, Olga

[Megha Dutta]

Hi Olga 

Bulk edit issue is resolved.

[Megha Dutta]

Re-indexing done yesterday.

Jira updated in September

Yes VM is strong and DB is healthy

We are monitoring instances.

[Olga Videc]

Hello Megha

Have you tried with different browser?

BR, Olga

[Megha Dutta]

Hello Olga.

I tried through only chrome.

[Olga Videc]

Please try, Firefox and Edge, there could be some add on or something blocking your view, it happens to me when I have too many tabs open and since crome is quite demanding on resources.

[Megha Dutta]

Ok will try 

[Megha Dutta]

One more thing this is also showing when we open any saved filter

[Megha Dutta]

[Olga Videc]

Hello @Megha Dutta 

Can you re-upload the image?

[Megha Dutta]

[Olga Videc]

Hello @Megha Dutta 

There is something wrong with your browser or your instance please check links provided below the same issue is discussed, you may include your sysadmin if your browser is not the problem.

Answer provided by Atlassian 

found here 

https://community.atlassian.com/t5/Jira-questions/The-JIRA-server-could-not-be-contacted-This-may-be-a-temporary/qaq-p/158813

"This commonly seems to be an error displayed client-side by the browser Javascript. I would suggest trying our Troubleshooting Browser Problems KB (https://confluence.atlassian.com/display/JIRAKB/Troubleshooting+problems+in+the+browser) and also try enabling safe mode on the browser and even clearing your cache. You could also test with other browsers to see if there's any difference between them.

If you find it happens periodically, you can try taking a thread dump and also enabling garbage collection logging to see if there's any performance problems on the instance. Also check to see what's happening with your server when JIRA is slow - a high CPU can often mean GC is going nuts, which can be a result of not enough heap, a bug or a naughty plugin that has decided to use up more memory than it should. These will help:

https://confluence.atlassian.com/display/JIRAKB/Garbage+Collection+Performance+Problems

https://confluence.atlassian.com/display/JIRA/Generating+a+Thread+Dump"

https://confluence.atlassian.com/jirakb/operations-that-are-related-to-user-lookup-resulting-in-the-jira-server-could-not-be-contacted-this-may-be-a-temporary-glitch-or-the-server-may-be-down-error-941365405.html