BigW Consortium Gitlab
When we are filtering by a single project, and the current user has access to see confidential issues on that project, we don't need to filter by confidentiality at all - just as if the user were an admin. The filter by confidentiality often picks a non-optimal query plan: for instance, AND-ing the results of all issues in the project (a relatively small set), and all issues in the states requested (a huge set), rather than just starting small and winnowing further.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
README.md | Loading commit data... | |
access_requests_finder.rb | Loading commit data... | |
branches_finder.rb | Loading commit data... | |
contributed_projects_finder.rb | Loading commit data... | |
environments_finder.rb | Loading commit data... | |
events_finder.rb | Loading commit data... | |
group_finder.rb | Loading commit data... | |
group_members_finder.rb | Loading commit data... | |
group_projects_finder.rb | Loading commit data... | |
groups_finder.rb | Loading commit data... | |
issuable_finder.rb | Loading commit data... | |
issues_finder.rb | Loading commit data... | |
joined_groups_finder.rb | Loading commit data... | |
labels_finder.rb | Loading commit data... | |
members_finder.rb | Loading commit data... | |
merge_requests_finder.rb | Loading commit data... | |
milestones_finder.rb | Loading commit data... | |
move_to_project_finder.rb | Loading commit data... | |
notes_finder.rb | Loading commit data... | |
personal_access_tokens_finder.rb | Loading commit data... | |
personal_projects_finder.rb | Loading commit data... | |
pipeline_schedules_finder.rb | Loading commit data... | |
pipelines_finder.rb | Loading commit data... | |
projects_finder.rb | Loading commit data... | |
snippets_finder.rb | Loading commit data... | |
tags_finder.rb | Loading commit data... | |
todos_finder.rb | Loading commit data... | |
union_finder.rb | Loading commit data... | |
users_finder.rb | Loading commit data... |