GLQL advanced finder, remove project_ids
What does this MR do and why?
This MR removes the project ID collection because it's not needed to query work items using advanced search anymore.
The confidential filters were converted to using traversal id + project id for authorization and no longe rely upon the project id list (all linked issues below)
References
- Related to Fix GLQL ES performance regression: optimize `p... (#592420 - closed)
- Performance degradation for GLQL views (#592405 - closed)
- Search confidential filter should use traversal... (#558781 - closed)
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
- setup elasticsearch in GDK
- enable/configure advanced search
- enable FF
glql_es_integration - create a few confidential issues and epics
- create an issue or epic with GLQL in it
- make sure that the confidential issue or epic can come back in the list
I created this hierarchy with pairs of confidential/non-confidential issues and epics in each group/project:
top level - public <-- user GUEST
- sub group - internal
- project - internal
- sub group private
- project private <-- user REPORTER
Compared what the admin user can see and what the user can see
display: table
title: test confidential issues/epics
fields: title, confidential
query: group = "top-level-public"
admin
user
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Terri Chu

