Issuefunction to run faster

[Choo Kai Min Bryan]

I am a user and an advanced search with the help of issuefunction. I used the results in the query and made 4 gadgets and to a dashboard.

Apparently the admin told me that the query would slow down the system and would have the possibility of crashing the system if too many people use the dashboard. Our company uses Jira to track our patients therefore we have 100,000+ issues. The admin found that the query had to search them and if many users were using the dashboard , it would crash.

Is there a way to solve this ?

The query is sort of , Project = Task and issuefunction in linkedissuesof("issuetype = \"client\" and \"Client Service Type\" = \"Manager\"")

[Merle Fischer · Accepted solution]

it's not just about the amount of tickets searched through, but also about the tickets being displayed due to the filter. I'd recommend this page in the documentation to get a better idea of the realtionship between performance and JQL: https://confluence.atlassian.com/jirakb/understanding-jql-performance-740263450.html

plus any query that is ultamtely a nested one impacts performance especially.

[Choo Kai Min Bryan]

The document was very insightful and answered some of my questions and how the system works. I will try these out , thank you!

[Merle Fischer]

glad I could point you in the right direction ;)! Best of luck.

[Choo Kai Min Bryan]

So what you meant is to limit the amount of issues it has to search therefore having a quicker searchsearch? I was thinking of that , but was unsure if it would significantly speed up the search.

I have actually searched with issues with a specific status , Open. I would try to limit the searches better hopefully to speed things up. But other than that is there nothing else? 

[Merle Fischer]

one way is to limit it down to have the gadgets display only issues that are still unresolved, in order to do so just add: "AND resolution = EMPTY" (assuming that you always set a resolution when an issue has reached resolved or close status)
If you additionally want to include issues in those gadgets that have recently been resolved, try changing your query to something like "AND (resolution=EMPTY or resolutiondate >= -30d)"
This will then display all issues that have yet to be resolved or been resolved in the past month.

But this is just a bit of guesswork. What tickets should ideally be displayed in these dashboard gadgets, try thinking of factors that could limit the number of issues that needed to be displayed that alwasy helps in creating a good query with reagrds to performance.

Hope this helps, best

Merle

[Choo Kai Min Bryan]

Also having gadgets who uses Issue function , would it slow down the system too much ?

[Merle Fischer]

not necessarily it really comes down to how complicated your filter query is (so try to limit things in parantheses and too complicated AND OR combinations), and of course the number of issues that have to be display based on said filter, too many issues to be displayed causes the system to have trouble.