Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Diagnosing a slow loading JIRA issue

I have a series of JIRA issues which take as much as 7 seconds to load, and I want to understand what is causing the performance issue.

When profiling the performance of the page, I notice that there are two identical calls which contain most of the loading times: Retrieve From cache/db and filter.

Is there a way to dig into what's actually happening during these calls? I assume that I need a greater level of detail to understand why some, but not all issues, take so long to be read from the cache.

[0ms] - PermissionManager.getProjectObjects()
[0ms] - PermissionManager.hasPermission()
[0ms] - PermissionManager.hasPermission()
[0ms] - PermissionManager.hasPermission()
[0ms] - PermissionManager.hasPermission()
[0ms] - PermissionManager.hasPermission()
[2145ms] - Retrieve From cache/db and filter
[104ms] - Lucene Search
[0ms] - IssueIndexManager.getIssueSearcher()
[104ms] - Lucene Query
[2159ms] - Retrieve From cache/db and filter
[112ms] - Lucene Search

2 answers

1 accepted

0 votes
Answer accepted

For posterity, there was a condition using a JQL query that was causing the slow loading.

This was the reason for the page being slow to load and not just for actions such as transitions.

Hi Daniel, how did you find out which JQL it was?

We experience the same. When clicking on an issue in an Agile board, the issue is shown within half a second, but when I open the issue in a new tab, it takes 6 to 7 seconds to open. Opening the Agile board itself also costs about 10 secs.

Hi Daniel, can you please provide more details about "there was a condition using a JQL query that was causing the slow loading". How JQL condition is related to Issue load time? Was it caused by any plugin?

@DanielG - what condition using a JQL query?  a search condition or a plugin that was specifically making the call? @M_ Hoogenboom and @Aliaksei Shorkin and I all appear to be in the same boat... not sure if they found anything out at this point... 

Any assistance appreciated.

With the caveat that this was a few years ago - there was some trickery being done where the transition options were based on JQL queries, in a project which had issue-level security enabled, so Jira ran the query on page load and it was really expensive.

0 votes
Gaston Valente Community Leader Jul 15, 2017


Sometimes certain plugins slows down the loading if the issue has a large change history, the only way I know to get more level of detail is by using a profiler like jprofiler.

i had this problems several time, what I do is:

  1. try to find what the slow issues had in common
  2. turn on safe mode disabling all the plugins and set a baseline for loading times
  3. start one by one each plugin while measuring the performance impact of each one

But first of all make sure your db connectivity and latency are correct and the io performance is ok based on atlassian parameters ( there's an io testing tool from atlassian)

hope you can find the solutions, this problems gave all of us insight to solve future problems 

is this a very large instance?


Suggest an answer

Log in or Sign up to answer

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you