Backend for advanced search merge request target-branch facet
The target_branch
field currently exists on the merge_request document
- Pass down new param to
MergeRequestClassProxy
- Add a new feature flag
- Update
MergeRequestClassProxy
behind the FF to:
- if
=
: add filter for target_branch = target_branch - if
!=
: add must_not for target_branch = target_branch
questions to answer
- decide how to handle the
=
and!=
cases. options are:
-
target_branch
andnot_target_branch
-
not[target_branch]
andtarget_branch
- are there any users without access to see branches for a project? or group? this will this affect whether the filter is available or what populates it
Edited by Terri Chu