PermissionQueryFactory can cause performance issues when JIRA's caches are cold

Summary

Large instances of JIRA will experience performance problems when a query for a project share is constructed (this is used for example to share saved filters on a view rapid board screen). The impact will be higher in proportion to quantity of projects and associations between users and roles (role actors).

Cause

The way we are checking whether the user has rights to view saved filters is highly inefficient and may cause performance problems on large instances (big number of projects and roles) resulting in a lot of database queries when JIRA's caches are cold.

Notes

One workaround for this issue is to keep the caches warm by running a curl script for example every 15 minutes. Example url: https://host:port/rest/greenhopper/1.0/xboard/config.json?returnDefaultBoard=false&rapidViewId=idOfSomeBoard