Support type, status and source/target branch/project fields in GLQL
What does this MR do and why?
Support type, status and source/target project fields in GLQL
Add support for fields in presenter:
MRs:
- sourceBranch (as code)
- targetBranch (as code)
- sourceProject (as link)
- targetProject (as link)
Issues/WorkItems:
- status (as custom status, EE only)
- type (as type)
Also upgrades @gitlab/query-language-rust
to v0.13.1. See CHANGELOG.
References
Closes gitlab-org/gitlab-query-language/glql-rust#51
Screenshots or screen recordings
Query | Screenshot |
---|---|
Merge request fields:
|
|
Issue / work item fields:
|
|
Querying by status:
|
|
Displaying issue/work item type
|
How to set up and validate locally
-
Enable custom statuses feature flag:
echo "Feature.enable(:work_item_status_feature_flag)" | rails c
-
In an issue description enter all the queries mentioned in the "Screenshots" section.
-
The tables should display as expected.
-
Enable GLQL work items feature flag
echo "Feature.enable(:glql_work_items)" | rails c
-
The tables should still display as expected with an "Experiment" badge.
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.