[WIP] Add team workflow page

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:

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.

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