From 61da3a6d13d2c202e24b64892a79ddb6675fa4ea Mon Sep 17 00:00:00 2001
From: A Thousand Ships <96648715+AThousandShips@users.noreply.github.com>
Date: Mon, 13 Oct 2025 13:53:06 +0200
Subject: [PATCH] Add team workflow page

---
 index.rst                |  1 +
 triage/team_workflow.rst | 26 ++++++++++++++++++++++++++
 triage/workflow.rst      | 19 +------------------
 3 files changed, 28 insertions(+), 18 deletions(-)
 create mode 100644 triage/team_workflow.rst

diff --git a/index.rst b/index.rst
index b13ae2e..187b569 100644
--- a/index.rst
+++ b/index.rst
@@ -45,6 +45,7 @@ for your topic of interest. You can also use the search function in the top-left
    triage/workflow
    triage/guidelines
    triage/release_blockers
+   triage/team_workflow
 
 .. toctree::
    :hidden:
diff --git a/triage/team_workflow.rst b/triage/team_workflow.rst
new file mode 100644
index 0000000..f3713bf
--- /dev/null
+++ b/triage/team_workflow.rst
@@ -0,0 +1,26 @@
+.. _doc_bug_triage_team_workflow:
+
+Team Triage Workflow
+====================
+
+Team Workflow
+-------------
+
+When issues arrive in the triage projects they will have the “For Team
+Assessment” status. These issues should be treated as being unverified,
+and should be verified before moving the issue to another status. This
+can be done as part of regular team meetings, or be handled by
+individual maintainers processing these, as long as the assessment made
+by triagers is verified.
+
+As part of this verification, other information should be updated if
+needed. For example, if the issue was added to multiple trackers because
+it was unclear what area it belongs to, it should be removed from the
+unrelated tracker(s). This is also a good time to verify any regression
+severity or assign one if it is unassessed.
+
+If the report is missing information, please ask the author for more
+details. If the task of handling testing updated information can be
+handled by the bugsquad, this task can be handed over to them for
+verification: for example, testing an updated MRP provided by the
+author.
diff --git a/triage/workflow.rst b/triage/workflow.rst
index 06be5d6..d5d868d 100644
--- a/triage/workflow.rst
+++ b/triage/workflow.rst
@@ -179,24 +179,7 @@ an issue is closed, regardless of how it was solved.
 Team Workflow
 -------------
 
-When issues arrive in the triage projects they will have the “For Team
-Assessment” status. These issues should be treated as being unverified,
-and should be verified before moving the issue to another status. This
-can be done as part of regular team meetings, or be handled by
-individual maintainers processing these, as long as the assessment made
-by triagers is verified.
-
-As part of this verification, other information should be updated if
-needed. For example, if the issue was added to multiple trackers because
-it was unclear what area it belongs to, it should be removed from the
-unrelated tracker(s). This is also a good time to verify any regression
-severity or assign one if it is unassessed.
-
-If the report is missing information, please ask the author for more
-details. If the task of handling testing updated information can be
-handled by the bugsquad, this task can be handed over to them for
-verification: for example, testing an updated MRP provided by the
-author.
+For team triage workflow, see :ref:`doc_bug_triage_team_workflow`.
 
 .. [1]
    This is limited to PRs on the ``master`` branch, for other cases