Hi Triage Team, Here is a list of the issues that do not meet the triaged criteria in accordance with the [Partial triage guidelines](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#partial-triage), we would like to ask you to: 1. If the issue is spam, [report the abuse](https://docs.gitlab.com/ee/user/abuse_reports.html) and make the issue confidential. Flag the report that is raised in the [`#abuse`](https://gitlab.slack.com/messages/C0HPYBJ3D) Slack channel with a link to the issue and alert the `@abuse-team`. 1. If the issue is a request for help, you can use this template to provide resources and close the issue: ``` Hey @author. Based on the information given, this request for support is out of the scope of the issue tracker (which is for new bug reports and feature proposals). Unfortunately, I won't be able to help get it resolved. However, for support requests we have several resources that you can use to find help and support from the Community, including: * [Technical Support for Paid Tiers](https://about.gitlab.com/support/) * [Community Forum](https://forum.gitlab.com/) * [Reference Documents and Videos](https://about.gitlab.com/get-help/#references) Please refer to our [Support page](https://about.gitlab.com/support/) for more information. If you believe this was closed in error, please feel free to re-open the issue. /label ~"support request" /close ``` * If the issue is re-opened after you closed it, you should get an email notification and would then be responsible for re-evaluating the issue. * (Optional) Alternatively, instead of closing the issue when using the template above, you could take on the role of customer support and ask the reporter for more information so we can properly assist them. If you do this, add the ~"awaiting feedback" label. 1. Check for [duplicate issues](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#duplicates). If identified as a duplicate, the new issue can be closed with a note similar to: ``` Hey @author. Thanks for creating this issue, but it looks like a duplicate of #issue. I'm closing this issue in favour of #issue. Please add your thoughts and feedback on #issue (don't forget to upvote feature proposals). /duplicate #issue ``` * Do not make any forward looking statements around milestone targets that the duplicate issue may be assigned. 1. If it is unclear whether the issue is a bug or a support request: * `@mention` the PM/EM for the [relevant group](https://about.gitlab.com/handbook/product/product-categories/#devops-stages) and ask for their opinion. 1. Add a [type label](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#type-labels). * If identified as a bug, add a [severity label](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#severity-labels). * If the severity is ~"severity::1" or ~"severity::2", [mention relevant PM/EMs from the relevant stage group from product devstages categories](https://about.gitlab.com/handbook/product/categories/#devops-stages). 1. Add a [stage label](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#stage-labels). 1. Add a [group label](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#group-labels). 1. Add relevant [category](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#category-labels) labels to facilitate automatic addition of stage and group labels. 1. If needed, [mention relevant domain experts](https://about.gitlab.com/company/team/structure/#expert) if the issue requires further attention. 1. (Optional) Mention relevant PM/EMs from the relevant stage group from [product devstages categories](https://about.gitlab.com/handbook/product/product-categories/#devops-stages). For the issues triaged please check off the box in front of the given issue. Once you've triaged all the issues assigned to you, you can unassign and unsubscribe yourself via these quick actions: ``` /done /unassign me /unsubscribe ``` **When all the checkboxes are done, close the issue, and celebrate!** :tada: @at.ramya - [x] gitlab-org/gitlab#352524 Failure in browser_ui/3_create/merge_request/cherry_pick/cherry_pick_a_merge_spec.rb | Create Cherry picking from a merge request creates a merge request ~"QA", ~"Quality", ~"failure::investigating", ~"found:main", ~"priority::2", ~"test" - [x] gitlab-org/gitlab#352519 Public Epic dates are not visible in the side panel if user is not part of the group - [x] gitlab-org/gitlab#352513 CI job on a Windows machine does not execute all steps of the `script` block - [x] gitlab-org/gitlab#352502 (confidential) ~"(confidential)" @jo_shih - [ ] gitlab-org/gitlab#352608 Group level variables environment_scope should be tier instead of environment - [ ] gitlab-org/gitlab#352602 REST API does not include "Require associated issue in Jira" field, despite it being available in the UI - [ ] gitlab-org/gitlab#352590 Parent pipeline status "failed" when child has only manual jobs - [ ] gitlab-org/gitlab#352586 Confusing dialogue when editing issue comments, "cancel" means "do not cancel" @kwiebers - [ ] gitlab-org/gitlab#352585 Inbound generated email address length does not adhere to RFC standard. - [ ] gitlab-org/gitlab#352582 Inconsistent and incorrect use of env. prefix before Gitlab predefined variables in Maven repository page - [ ] gitlab-org/gitlab#352578 Notification for Releases when using the Microsoft Teams Integration Plugin - [ ] gitlab-org/gitlab#352576 REST API v4: Session cookie does not grant all permissions @vincywilson - [x] gitlab-org/gitlab#352573 Compare changes - source and target tag ( you should switch sides in `compare/.......?view=parallel` ) ~"Category:Source Code Management", ~"automation:ml", ~"automation:ml wrong", ~"devops::create", ~"group::source code", ~"section::dev" - [x] gitlab-org/gitlab#352572 doc (?): variables to docker job runners passed differently than doc says wrt to variables to service containers - [x] gitlab-org/gitlab#352538 Failure in browser_ui/3_create/web_ide/add_file_template_spec.rb | Create Web IDE file templates user adds .gitignore via file template Android ~"QA", ~"Quality", ~"devops::create", ~"failure::investigating", ~"found:main", ~"priority::2", ~"section::dev", ~"test" - [x] gitlab-org/gitlab#352527 cannot update my email address when using social sign-in --- Job URL: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/2103246132 This report was generated from [this policy](https://gitlab.com/gitlab-org/quality/triage-ops/blob/master/policies/stages/report/untriaged-issues.yml)