HI Nicole,
I understand you have a single Service Desk project that appears to be much slower than the others. It can be difficult to say the exact cause here without more data.
But I have a hunch or two of things to look for, such as number of SLAs created in that project, number of issues in the queue, and JQL filter complexity of that queue.
Each JSD project can have it's own set of SLAs, it's possible that having lots of these can cause performance problems when trying to load that project. Check out the KB How to Troubleshoot SLAs in JIRA Service Desk. There is a section there called SLA Rule Overload that can help identify if this is the case.
If this isn't helpful, I'd be interested to learn how many issues exist in this specific project, you can find that in the issue navigator just by doing a search such as
project=xyz
where xyz is the project key here.
Lastly, if the first page you see that loads when you visit this project is the queues page, then it could be the complexity of those queues that could cause long page loads. You can see this in more detail in Make queues for your team. By default these queues use simple searches, but if you customize these to use very long and complex JQL searches it can really add up when trying to load the page itself.
I hope this helps.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.