@@ -15,6 +15,27 @@ Triagers may choose to subscribe to the `~C0Workflow::Backlog` label and/or peri
The [Automate the Customer Zero Triage Process](https://gitlab.com/groups/gitlab-com/gl-security/product-security/product-security-engineering/-/epics/45) epic automated each manual step below by leveraging [gitlab-triage](https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage) and GitLab Duo. For most cases, each new issue should be triaged without manual intervention but in the event GitLab Duo is unable to determine the responsible team, Duo will comment this fact and mention the [Product Security Engineering](/handbook/security/product-security/security-platforms-architecture/product-security-engineering/) team who will triage the issue using the steps below.
### Temporary workaround process
In the event the automated triaging is not working, you can ask Duo to suggest a team by:
1. Ensure the page you're on is the Work item that needs triaging.
1. Bring up Duo chat and paste in the following prompt:
```plain
Please determine which team is responsible for this GitLab Issue out of the following list of teams:
* Application Security Team
* PSIRT
* Vulnerability Management Team
* Product Security Engineering Team
* Security-Platforms-Architecture Team
Ensure the responsible team is formatted **<TEAM>insert team name here</TEAM>**.
```
1. Use the response from Duo to guide the team labels to apply.
### Manual steps
1. Select an issue that does NOT start with the prefixes `DRAFT:` or `WIP:`. Those issues are ones that submitters have started, but they still need to provide additional information before we review them. That's fine! We'd prefer to have visibility into what's coming anyway.
