There are myriad ways to misconfigure a cloud instance of Jira. You thought I was referring to the configuration of the actual web app I suppose. That's kind of

There are myriad ways to misconfigure a cloud instance of Jira. You thought I was referring to the configuration of the actual web app I suppose. That's kind of a silly assumption but gives me a lot of insight into what you've said here... A quote from a funny TV show still doesn't really make it a thing, does it? I don't know that this is the way to fix what you believe to be an open issue. It probably is: https://community.atlassian.com/t5/Jira-Questions/Hide-Closed-Epics-from-backlog-view/qaq-p/625966 https://community.atlassian.com/t5/Jira-Questions/Hide-Close... If it's not, there probably is a way to do what you are trying to do that you just don't know about. I work at a very large organization. The user lookups in Jira are lightning fast & the permissions are granular for a reason. Can't help you with your billing problems but it kind of sounds like a "you" problem. I have fully configured a Service Desk instance, yes. It sounds like maybe you aren't actually using the release feature & or that maybe you don't know how to write JQL queries or maybe I don't know anything about the amazingly advanced way you are trying to use the features. "Hey doc, my arm hurts when I do this?" The doctor says "Then don't do it." I could keep going too but it would be a waste of my time to try & have a reasonable discussion on something which you have prononuced your verdict: "Atlassian is a bunch of decent products drowning in scope creep, terrible cross-product integration, and a painfully slow development cycle that is focused way more on cosmetic features that fixes their trainwreck of a dumpster fire." All generalizations are false...