Performance issue with JIRA 6.2.5

We currently have a valid license with JQL Tricks for Live Nation Entertainment.  We are finding that many of our queries take an extremely long time when using JQL Tricks in our JQL.

Is this because of this issue?  https://jira.atlassian.com/browse/JRA-36368

 

We have over 6,000 users using our JIRA instance where a handful of them are creating many filter queries. Is there a standard document your team can suggest in writing queries I can share with my users? Some of their queries take an extremely long time to return results.

Here is one of them:

project = MFOL AND (cf[10863] = Bergman OR cf[10863] = "All Teams" OR issue in parent("cf[10863] = Bergman OR cf[10863] = 'All Teams'")) ORDER BY Rank ASC

Can you share query creating best practices this can significantly help the JIRA experience within our global userbase.

 

5 answers

0 vote

You will find the usage guide here but that is more of syntax and not best practices. The general rule is to keep the result set small and that will improve the performance.

For example, if you have 100K issues returning from the "parent" function, it will take more time than when it returns 1000 issues. In the above query, looks like you are expecting to see only issues from MFOL project and so you can include that criteria inside the parent function. Updated query will look like:

project = MFOL AND (cf[10863] = Bergman OR cf[10863] = "All Teams" OR issue in parent("(cf[10863] = Bergman OR cf[10863] = 'All Teams') AND project = MFOL")) ORDER BY Rank ASC

That aside, JQL Tricks has a couple of configurations you can set globally.

  1. You can restrict the functions to certain users.
  2. You can restrict the functions to selected projects

Both limits the functionality and so not sure if that is an option. If not, stick to writing limiting queries and vote on https://jira.atlassian.com/browse/JRA-39375 wink

Hi Jobin,

Thank you for the information.  We want to upgrade our instance from JIRA 6.2.5 but need to know which version of JIRA we should upgrade to.  Is JIRA-36368 issue resolved in the version of JIRA 6.3.14 which is the latest?

Regards,

Adolfo

https://jira.atlassian.com/browse/JRA-36368 is resolved in 6.3.4+. JRA-39375 is another one I would keenly watch!

Jobin,

 

Just a quick update.....thoughts?  There is a performance improvement but not as much as we expected.

 

We have upgraded to JIRA version 6.3.14 in our DEV instance and compared the following query which returns 4115 issues:

 

project = MFOL AND (cf[10863] = Bergman OR cf[10863] = "All Teams" OR issue in parent("cf[10863] = Bergman OR cf[10863] = 'All Teams'")) ORDER BY Rank ASC

 

DEV /JIRA = 14 secs.  (JIRA version 6.2.5)

DEV /JIRA3 = 9 secs   (JIRA version 6.3.14)

PROD /JIRA = 38 secs.  (JIRA version 6.2.5)

 

Your modified query:  project = MFOL AND (cf[10863] = Bergman OR cf[10863] = "All Teams" OR issue in parent("(cf[10863] = Bergman OR cf[10863] = 'All Teams') AND project = MFOL")) ORDER BY Rank ASC

 

DEV /JIRA = 18 secs.  (JIRA version 6.2.5)

DEV /JIRA3 = 8 secs   (JIRA version 6.3.14)

PROD /JIRA = 35 secs.  (JIRA version 6.2.5)

 

Our prod instance is on a bare metal server and DEV on a VM.  This query was run during the evening when less users on JIRA.

 

-Adolfo

I have seen better numbers but that is when the queries were taking over a minute. Having said that, the biggest improvement will only come when JRA-39375 is implemented. I am waiting for that fix too.

Jobin,

This query returns a small set of issues but takes an extremely long time.  How would you optimize?  There are many JIRA users writing queries like this which takes a toll on our JIRA instance.

project = "Win Team SA" AND (status in (Open, "In Progress", Reopened, Scheduled, Blocked, Pending) OR status in (Resolved, Closed, Verified, Confirmed) AND updated >= startOfWeek(-1d)) OR Assignee = "Ege.Test" AND (status in (Open, "In Progress", Reopened, Scheduled, Blocked, Pending) OR status in (Resolved, Closed, Verified, Confirmed) AND updated >= startOfWeek(-1d)) ORDER BY Rank ASC

-Adolfo

This is an example where you do not have any plugin functions. It is not the number of issues returned in the end. The key is to reduce the number of issues returned for each clause. What are you trying to do in this query?

It looks like they are trying to consolidate a few queries into one.  This is a filter for an Agile Kanban board.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published Apr 10, 2018 in Marketplace Apps

Learn about how Stefan K. built one of the *first ever* Marketplace apps

In this post you will discover more about the evolution of K15t software, some big topics they're currently focusing on in the app space, and a rare (not not funny!) photo of founders Mike Cannon-Bro...

13,092 views 11 24
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you