GitLab issueshttps://gitlab.com/gitlab-org/gitlab/-/issues2024-03-29T04:55:10Zhttps://gitlab.com/gitlab-org/gitlab/-/issues/452478[Test] ee/spec/requests/api/graphql/boards/board_list_query_spec.rb | Queryin...2024-03-29T04:55:10ZTEST_FAILURES_PROJECT_TOKEN[Test] ee/spec/requests/api/graphql/boards/board_list_query_spec.rb | Querying a Board list when the user has access to the list is expected to include {issuesCount => 2, title => foo}### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`ee/spec/requests/api/graphql/boards/board_list_query_spec.rb#L47`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/spec/requests/api/graphql/boa...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`ee/spec/requests/api/graphql/boards/board_list_query_spec.rb#L47`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/spec/requests/api/graphql/boards/board_list_query_spec.rb#L47) |
| Filename | `ee/spec/requests/api/graphql/boards/board_list_query_spec.rb` |
| Description | `Querying a Board list when the user has access to the list is expected to include {"issuesCount" => 2, "title" => "foo"}` |
| Test level | integration |
| Hash | `6580ae0c478292e15e5fc4b6b42593a760f52f967` |
| Expected duration | < 19.2 seconds |https://gitlab.com/gitlab-org/gitlab/-/issues/452472[Test] spec/requests/api/graphql/notes/note_spec.rb | Query.note(id) when the...2024-03-29T02:44:58ZTEST_FAILURES_PROJECT_TOKEN[Test] spec/requests/api/graphql/notes/note_spec.rb | Query.note(id) when the user has access to read the note when note is internal and user can read confidential notes returns note### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/requests/api/graphql/notes/note_spec.rb#L96`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/requests/api/graphql/notes/note_spec.rb#L96...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/requests/api/graphql/notes/note_spec.rb#L96`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/requests/api/graphql/notes/note_spec.rb#L96) |
| Filename | `spec/requests/api/graphql/notes/note_spec.rb` |
| Description | `Query.note(id) when the user has access to read the note when note is internal and user can read confidential notes returns note` |
| Test level | integration |
| Hash | `fc11659456233c624391f84a0f0cfed977ceaa35a` |
| Expected duration | < 19.2 seconds |https://gitlab.com/gitlab-org/gitlab/-/issues/452459When namespace_in_path is enabled and auth_redirect_uri is manually updated t...2024-03-28T21:35:38ZNaman Jagdish GalaWhen namespace_in_path is enabled and auth_redirect_uri is manually updated to non-projects url, auth flow fails### Summary
When `namespace_in_path` is enabled and `auth_redirect_uri` is manually updated to a non-projects URL, the authentication flow fails. The user gets redirected to GitLab and back to Pages. However, Pages then issues a redirec...### Summary
When `namespace_in_path` is enabled and `auth_redirect_uri` is manually updated to a non-projects URL, the authentication flow fails. The user gets redirected to GitLab and back to Pages. However, Pages then issues a redirect back to itself, adding a '/' at the end. This results in a situation of TOO_MANY_REDIRECTS, where every redirect adds a new '/' to the end of the request.
Build version: v16.10.0
### Steps to reproduce
Configuration is given here: https://gitlab.com/gitlab-org/gitlab/-/issues/434372#note_1834860095
### Example Project
### What is the current _bug_ behavior?
The user gets redirected to GitLab and back to Pages. However, Pages then issues a redirect back to itself, adding a '/' at the end. This results in a situation of TOO_MANY_REDIRECTS, where every redirect adds a new '/' to the end of the request.
### What is the expected _correct_ behavior?
The authentication flow should complete, allowing the user to access the pages after entering their credentials.
### Relevant logs and/or screenshots
### Output of checks
#### Results of GitLab environment info
<details>
<summary>Expand for output related to GitLab environment info</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:env:info\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\`)
</pre>
</details>
#### Results of GitLab application Check
<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`)
(For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
(we will only investigate if the tests are passing)
</pre>
</details>
### Possible fixeshttps://gitlab.com/gitlab-org/gitlab/-/issues/452444[Test] ee/spec/features/labels_hierarchy_spec.rb | Labels Hierarchy scoped bo...2024-03-28T18:54:07ZTEST_FAILURES_PROJECT_TOKEN[Test] ee/spec/features/labels_hierarchy_spec.rb | Labels Hierarchy scoped boards for project boards behaves like filter for scoped boards scopes board to ancestor and current group labels### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`ee/spec/features/labels_hierarchy_spec.rb#L80`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/spec/features/labels_hierarchy_spec.rb#L80) |
| ...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`ee/spec/features/labels_hierarchy_spec.rb#L80`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/spec/features/labels_hierarchy_spec.rb#L80) |
| Filename | `ee/spec/features/labels_hierarchy_spec.rb` |
| Description | `Labels Hierarchy scoped boards for project boards behaves like filter for scoped boards scopes board to ancestor and current group labels` |
| Test level | system |
| Hash | `31b13ee527b8880c4a5efb498d840889093692a8c` |
| Reference duration | 190.33 seconds |
| Expected duration | < 50.13 seconds |
### Stack trace
```
Shared Example Group: "filter for scoped boards" called from ./ee/spec/features/labels_hierarchy_spec.rb:80
```
### Reports (1)
1. 2024-03-28: https://gitlab.com/gitlab-org/gitlab/-/jobs/6504613860 (https://gitlab.com/gitlab-org/gitlab/-/pipelines/1232318967)https://gitlab.com/gitlab-org/gitlab/-/issues/452438[Test] ee/spec/features/projects/analytics/cycle_analytics_spec.rb | Project ...2024-03-28T18:53:51ZTEST_FAILURES_PROJECT_TOKEN[Test] ee/spec/features/projects/analytics/cycle_analytics_spec.rb | Project > Value stream analytics with cycle_analytics_for_projects licensed feature available with no value stream allows to create a custom value stream### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`ee/spec/features/projects/analytics/cycle_analytics_spec.rb#L70`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/spec/features/projects/analyti...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`ee/spec/features/projects/analytics/cycle_analytics_spec.rb#L70`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/spec/features/projects/analytics/cycle_analytics_spec.rb#L70) |
| Filename | `ee/spec/features/projects/analytics/cycle_analytics_spec.rb` |
| Description | `Project > Value stream analytics with cycle_analytics_for_projects licensed feature available with no value stream allows to create a custom value stream` |
| Test level | system |
| Hash | `58b85e74910d8d4b9d022c03ffbfedd19e12def7a` |
| Reference duration | 189.7 seconds |
| Expected duration | < 50.13 seconds |
### Stack trace
```
Capybara::ElementNotFound: Unable to find visible field "Value Stream name" that is not disabled
Timeout (30s) reached while running a waiting Capybara finder.
Consider using a non-waiting finder.
See https://www.cloudbees.com/blog/faster-rails-tests
```
### Reports (1)
1. 2024-03-28: https://gitlab.com/gitlab-org/gitlab/-/jobs/6504613860 (https://gitlab.com/gitlab-org/gitlab/-/pipelines/1232318967)https://gitlab.com/gitlab-org/gitlab/-/issues/452424Add `Beta` badge to AI impact analytics dashboard2024-03-28T21:02:06ZAlex PennellsAdd `Beta` badge to AI impact analytics dashboardRelated thread: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/148078#note_1834925912Related thread: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/148078#note_183492591216.11https://gitlab.com/gitlab-org/gitlab/-/issues/452420Add development widget to required work item types in the DB2024-03-28T18:31:58ZMario CeliAdd development widget to required work item types in the DBBefore we are able to query or set data on work items via the development widget, we need to make it available at the work item type level and this is configured in the DB.
We need a migration to introduce the widget definition in exis...Before we are able to query or set data on work items via the development widget, we need to make it available at the work item type level and this is configured in the DB.
We need a migration to introduce the widget definition in existing installs and update the seeder to include the new widget in new installs16.11Mario CeliMario Celihttps://gitlab.com/gitlab-org/gitlab/-/issues/452416[Test] ee/spec/requests/api/graphql/project/issues_spec.rb | getting an issue...2024-03-28T17:41:24ZTEST_FAILURES_PROJECT_TOKEN[Test] ee/spec/requests/api/graphql/project/issues_spec.rb | getting an issue list for a project behaves like graphql issue list request spec EE filtering when filtering by epic when filtering for issues without epics returns all issues without epics### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`ee/spec/requests/api/graphql/project/issues_spec.rb#L24`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/spec/requests/api/graphql/project/issu...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`ee/spec/requests/api/graphql/project/issues_spec.rb#L24`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/spec/requests/api/graphql/project/issues_spec.rb#L24) |
| Filename | `ee/spec/requests/api/graphql/project/issues_spec.rb` |
| Description | `getting an issue list for a project behaves like graphql issue list request spec EE filtering when filtering by epic when filtering for issues without epics returns all issues without epics` |
| Test level | integration |
| Hash | `edd1eb6d8d66d4f8420c7eee4e9c015cd200df60e` |
| Reference duration | 3.09 seconds |
| Expected duration | < 19.2 seconds |https://gitlab.com/gitlab-org/gitlab/-/issues/452409New GQL query to list linked feature flags through the development widget2024-03-28T22:52:28ZMario CeliNew GQL query to list linked feature flags through the development widgetNew development widget should be available for work items in GraphQL. A field in the development widget should allow to paginate a list of associated feature flagsNew development widget should be available for work items in GraphQL. A field in the development widget should allow to paginate a list of associated feature flags16.11Mario CeliMario Celihttps://gitlab.com/gitlab-org/gitlab/-/issues/452408New mutation to link a work item with a feature flag2024-03-28T17:19:12ZMario CeliNew mutation to link a work item with a feature flagNew input available on create/update work item mutation. Development widget input should allow passing a list of feature flag IDs in order to associate them with the work itemNew input available on create/update work item mutation. Development widget input should allow passing a list of feature flag IDs in order to associate them with the work itemhttps://gitlab.com/gitlab-org/gitlab/-/issues/452382Allow for more interpolation options when generating the panel title2024-03-28T18:02:16ZAlex PennellsAllow for more interpolation options when generating the panel titleFrom this comment: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/148078#note_1834994810
Currently only [namespaceName](https://gitlab.com/gitlab-org/gitlab/-/blob/451482-add-feature-flag/ee/app/assets/javascripts/vue_shared/comp...From this comment: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/148078#note_1834994810
Currently only [namespaceName](https://gitlab.com/gitlab-org/gitlab/-/blob/451482-add-feature-flag/ee/app/assets/javascripts/vue_shared/components/customizable_dashboard/panels_base.vue#L144) is supported, which is actually rootNamespaceName.
### Proposal:
- Rename `namespaceName` > `rootNamespaceName`
- Rename in existing dashboards
- Add new `namespaceName` interpolation option
- Add `namespaceType` which will interpolate to `Group` or `Project` based on the context16.11https://gitlab.com/gitlab-org/gitlab/-/issues/452377[Test] spec/requests/api/graphql/project/issues_spec.rb | getting an issue li...2024-03-28T15:16:13ZTEST_FAILURES_PROJECT_TOKEN[Test] spec/requests/api/graphql/project/issues_spec.rb | getting an issue list for a project behaves like graphql issue list request spec behaves like a working graphql query returns a successful response### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/requests/api/graphql/project/issues_spec.rb#L83`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/requests/api/graphql/project/issues_spe...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/requests/api/graphql/project/issues_spec.rb#L83`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/requests/api/graphql/project/issues_spec.rb#L83) |
| Filename | `spec/requests/api/graphql/project/issues_spec.rb` |
| Description | `getting an issue list for a project behaves like graphql issue list request spec behaves like a working graphql query returns a successful response` |
| Test level | integration |
| Hash | `d4a37c8c86a6c1b550639b09f90b2910a4706f57b` |
| Reference duration | 1.22 seconds |
| Expected duration | < 19.2 seconds |
### Stack trace
```
Shared Example Group: "a working graphql query" called from ./spec/support/shared_examples/requests/api/graphql/issue_list_shared_examples.rb:13
Shared Example Group: "graphql issue list request spec" called from ./spec/requests/api/graphql/project/issues_spec.rb:83
```
### Reports (1)
1. 2024-03-28: https://gitlab.com/gitlab-org/gitlab/-/jobs/6502019918 (https://gitlab.com/gitlab-org/gitlab/-/pipelines/1231961274)https://gitlab.com/gitlab-org/gitlab/-/issues/452363Mismatch when updating tasks in the description2024-03-28T17:53:42ZNicolas Dularndular@gitlab.comMismatch when updating tasks in the descriptionFrom: https://gitlab.com/gitlab-org/gitlab/-/issues/451453#note_1836271678
We don't sync updating tasks in descriptions yet. How to reproduce:
1. Create an epic with the feature flags enabled to also create a work item
2. Add a task to ...From: https://gitlab.com/gitlab-org/gitlab/-/issues/451453#note_1836271678
We don't sync updating tasks in descriptions yet. How to reproduce:
1. Create an epic with the feature flags enabled to also create a work item
2. Add a task to the description with `- [ ] ...`
3. Check/Uncheck the checkbox of the task -> see that it doesn't get synced
The reason is that we don't forward the `update_task` parameter:
![Screenshot_2024-03-28_at_14.27.52](/uploads/cf59c5466f48d137867aa6b7ce151754/Screenshot_2024-03-28_at_14.27.52.png)16.11https://gitlab.com/gitlab-org/gitlab/-/issues/452356GitLab for Jira Cloud app | issue ID format breaks when creating MR2024-03-28T12:07:34ZMarijn MensingaGitLab for Jira Cloud app | issue ID format breaks when creating MR### Summary
When using the Gitlab for Jira Cloud app we click the button "create pull request" to create a merge request in Gitlab.
The issue title is sent from Jira to Gitlab as the name of the MR. The problem is that this title does ...### Summary
When using the Gitlab for Jira Cloud app we click the button "create pull request" to create a merge request in Gitlab.
The issue title is sent from Jira to Gitlab as the name of the MR. The problem is that this title does not get url encoded before sending it to Gitlab resulting in broken Issue ID's in the MR. Without manual correction the newly created MR cannot be matched to the Jira issue.
### Steps to reproduce
1) Click "Create pull Request" on a random issue that is connected to Gitlab via the "Gitlab for Jira Cloud app"
![image.png](/uploads/7b88bb92db30384e18784077cdf3c780/image.png)
![image.png](/uploads/0199eb8b0cab0808dd402330188c522f/image.png)
2) You get redirected to the create Merge Request page of gitlab:
https://gitlab.com/someRepo/-/merge_requests/new?merge_request%5Bsource_branch%5D=PP-205-Demo-ticket
![image.png](/uploads/6890cbc68b8bdf1f4a39d0af9c827f0e/image.png)
3) As you can see "PP-205" gets wrongfully formated into "Pp 205". If it gets saved like this the integration with Jira breaks as Jira looks for MR with "PP-205" in the name and not "Pp 205"
### Example Project
### What is the current _bug_ behavior?
The title of the MR shows "Pp 205 Demo ticket"
![image.png](/uploads/991e42a4b95741678188bbbed9020b40/image.png)
### What is the expected _correct_ behavior?
The title of the MR shows "PP-205 Demo ticket"
![image.png](/uploads/f3583d7b3061cbf733d941d0fff5fe0b/image.png)
### Relevant logs and/or screenshots
\-
### Output of checks
\-
#### Results of GitLab environment info
<details>
<summary>Expand for output related to GitLab environment info</summary>
<pre>Gitlab cloud Jira cloud</pre>
</details>
#### Results of GitLab application Check
<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>
\\-
</pre>
</details>
### Possible fixes
The solution could maybe be sending an explicit `merge_request[title]` query param gets posted to Gitlab that is first url encoded. So the Issue ID is sent like: "PP%2D205" instead of "PP-205"https://gitlab.com/gitlab-org/gitlab/-/issues/452346Update documentation for available VSD visualization filters2024-03-28T22:49:20ZLorena CiutacuUpdate documentation for available VSD visualization filtersThe following discussion from !147714 should be addressed:
- [ ] @apennells started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147714#note_1830558339): (+1 comment)
> It looks like a new section was added...The following discussion from !147714 should be addressed:
- [ ] @apennells started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147714#note_1830558339): (+1 comment)
> It looks like a new section was added for this below, so we'll need to figure out what we want to do with the old one here. We originally decided to keep these filter docs within the DORA performers score section ([thread](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136497#note_1641697966)), so I'd imagine we'd still want to keep it here still. WDYT?
## Proposed solution
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147714#note_1835349250
* keep the current structure
* remove all the old YAML config docs when we [default enable the `group_analytics_dashboard_dynamic_vsd` feature flag](https://gitlab.com/gitlab-org/gitlab/-/issues/432185 "[Feature flag] Rollout of `group_analytics_dashboard_dynamic_vsd`")
* restructure / rewrite the docs once we [remove the `group_analytics_dashboard_dynamic_vsd`](https://gitlab.com/gitlab-org/gitlab/-/issues/441206 "Remove `group_analytics_dashboard_dynamic_vsd` feature flag")
## Related issues
https://gitlab.com/gitlab-org/gitlab/-/issues/414494+Next 1-3 releasesLorena CiutacuLorena Ciutacuhttps://gitlab.com/gitlab-org/gitlab/-/issues/452345Possibility to authenticate all GraphQL API calls2024-03-28T12:07:36ZLukáš Slánský (personal)Possibility to authenticate all GraphQL API calls### Proposal
It would be great to have the whole GraphQL API authenticated. Having the configuration possibility to return HTTP 401/403 for anonymous users calling the API.
### Background
I’m trying to harden the Community Edition and...### Proposal
It would be great to have the whole GraphQL API authenticated. Having the configuration possibility to return HTTP 401/403 for anonymous users calling the API.
### Background
I’m trying to harden the Community Edition and one of the weak points after the audit is “the Introspection is enabled”. I understand, that GraphQL is used extensively in the UI, so disabling the endpoint at all is not an option. Limiting the access to the authenticated users only (private server only - the SSO is enforced, no public repositories etc.).
<!-- Please add a label for the type of feature as per https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification -->https://gitlab.com/gitlab-org/gitlab/-/issues/452324[Test] spec/requests/api/graphql/project/issues_spec.rb | getting an issue li...2024-03-28T06:48:35ZTEST_FAILURES_PROJECT_TOKEN[Test] spec/requests/api/graphql/project/issues_spec.rb | getting an issue list for a project behaves like graphql issue list request spec filters when filtering by confidentiality when fetching non-confidential issues when user cannot see confidential...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/requests/api/graphql/project/issues_spec.rb#L83`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/requests/api/graphql/project/issues_spe...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/requests/api/graphql/project/issues_spec.rb#L83`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/requests/api/graphql/project/issues_spec.rb#L83) |
| Filename | `spec/requests/api/graphql/project/issues_spec.rb` |
| Description | `getting an issue list for a project behaves like graphql issue list request spec filters when filtering by confidentiality when fetching non-confidential issues when user cannot see confidential issues returns an empty list` |
| Test level | integration |
| Hash | `f288873f5e74a0b4dd83733ac4ed60db8fc670cf4` |
| Reference duration | 1.97 seconds |
| Expected duration | < 19.2 seconds |https://gitlab.com/gitlab-org/gitlab/-/issues/452311[Test] spec/workers/pages_worker_spec.rb | PagesWorker when called with any o...2024-03-28T04:04:58ZTEST_FAILURES_PROJECT_TOKEN[Test] spec/workers/pages_worker_spec.rb | PagesWorker when called with any other action does nothing### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/workers/pages_worker_spec.rb#L19`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/workers/pages_worker_spec.rb#L19) |
| Filename | `spec...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/workers/pages_worker_spec.rb#L19`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/workers/pages_worker_spec.rb#L19) |
| Filename | `spec/workers/pages_worker_spec.rb` |
| Description | `PagesWorker when called with any other action does nothing` |
| Test level | unit |
| Hash | `78b551a383c019742f919db2f74867ff0c57c4365` |
| Reference duration | 0.11 seconds |
| Expected duration | < 45.4 seconds |https://gitlab.com/gitlab-org/gitlab/-/issues/452310[Test] spec/workers/pages_worker_spec.rb | PagesWorker when called with the d...2024-03-28T04:04:56ZTEST_FAILURES_PROJECT_TOKEN[Test] spec/workers/pages_worker_spec.rb | PagesWorker when called with the deploy action calls UpdatePagesService### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/workers/pages_worker_spec.rb#L9`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/workers/pages_worker_spec.rb#L9) |
| Filename | `spec/w...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/workers/pages_worker_spec.rb#L9`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/workers/pages_worker_spec.rb#L9) |
| Filename | `spec/workers/pages_worker_spec.rb` |
| Description | `PagesWorker when called with the deploy action calls UpdatePagesService` |
| Test level | unit |
| Hash | `f8d72bd213ddeb562a1b95442536a775438e13d22` |
| Reference duration | 0.12 seconds |
| Expected duration | < 45.4 seconds |https://gitlab.com/gitlab-org/gitlab/-/issues/452298[Test] spec/features/issues/user_bulk_edits_issues_labels_spec.rb | Issues > ...2024-03-28T01:58:07ZTEST_FAILURES_PROJECT_TOKEN[Test] spec/features/issues/user_bulk_edits_issues_labels_spec.rb | Issues > Labels bulk assignment as an allowed user toggling a milestone setting a milestone keeps labels### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/features/issues/user_bulk_edits_issues_labels_spec.rb#L227`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/features/issues/user_bulk_ed...### Test metadata (don't modify)
| Field | Value |
| ------ | ------ |
| File URL | [`spec/features/issues/user_bulk_edits_issues_labels_spec.rb#L227`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/features/issues/user_bulk_edits_issues_labels_spec.rb#L227) |
| Filename | `spec/features/issues/user_bulk_edits_issues_labels_spec.rb` |
| Description | `Issues > Labels bulk assignment as an allowed user toggling a milestone setting a milestone keeps labels` |
| Test level | system |
| Hash | `4f9bdf063606431e93f5196dd2049cea41a1a5994` |
| Reference duration | 51.16 seconds |
| Expected duration | < 50.13 seconds |