3 ms·
It gets worse. You can modify those permissions, but every single Jira page that involves a permission check (and they get pretty granular) involves a nontrivia
by Karunamon 7y ago
It gets worse. You can modify those permissions, but every single Jira page that involves a permission check (and they get pretty granular) involves a nontrivial query to the user DB (which might, itself, involve a query to a backend like LDAP) to determine if you can do a thing or, critically, see the UI element to do the thing.
Best guidance when I was running Jiras were to restrict access at the network if at all possible, and don't use permissions any more than strictly necessary unless you like 5-10 seconds per page load. In other words, if only your developers need to see your Jira, don't grant only your developer group permissions, set it to "everyone" and lock everyone else out at the firewall.
- vultour 7y agoWe run massive JIRA instances with very granular permissions using multiple custom authorization backends (LDAP/Kerberos/in-house stuff), and it doesn't seem to add much of a delay.
- Karunamon 7y agoHm. Perhaps they took some time and worked on the performance then. It was ungodly slow a couple years back, and relaxing permissions led to a significant performance boost.
- bearer_token 7y agoThey've been touting performance increases for a while now https://confluence.atlassian.com/jirasoftware/jira-software-8-0-x-release-notes-957981626.html#JiraSoftware8.0.xreleasenotes-performance https://confluence.atlassian.com/jirasoftware/jira-software-...