Hi Atlassian community!
I'm having an issue where accessing the tempo planning application results in an indefinite spinner on the client. I've checked the network tab and it appears that tempo is trying to make almost 500 requests, one after another to access tempo planning info for users (we have a little less than 500 users, so that makes sense to me.) I say "indefinite," but I have waited the spinner out and after about 10 minutes all of the content renders.
What I don't understand is why this pegs the CPU of the host server to over 70% and potentially grinds the whole system to a halt. We run our Jira instance on a very beefy server. First off, I don't care to have a view of 500 users' planning info. I'd like to see my own. Second, I really don't think it should be taxing the system this badly to make such a request, but maybe I'm naive.
Any ideas? I'm running tempo planner version 7.18.1 on Jira server 8.5.0
