Skip to content
Snippets Groups Projects
Commit 89adab89 authored by Justin Stark's avatar Justin Stark
Browse files

Merge branch '6055-update-triage-step-to-add-label-for-priortization-and-kat-s-board' into 'master'

Resolve "Update Triage Step to Add Label for Priortization and Kat's Board"

Closes #6055

See merge request gitlab-com/www-gitlab-com!36690
parents 821602b9 da134d1e
No related branches found
No related tags found
No related merge requests found
Loading
Loading
@@ -436,6 +436,7 @@ Think of each of these groups of labels as ways of bucketing the work done. All
 
Optional labels that are useful to communicate state or other priority
* State (Red) (Won't Do, Blocked, Needs Consensus, etc.)
* Workflow Status (Workflow::Triage, Workflow::Ready, Workflow:: In Progress, Workflow:: Verification, Workflow:: Waiting)
* Inbound: For issues created by folks who are not on the data team; not for asks created by data team members on behalf of others
 
### Daily Standup
Loading
Loading
@@ -979,7 +980,10 @@ We also rotate Snowflake user passwords the first Sunday of every 3rd month of t
 
The data team has a triager who is responsible for:
* addressing `dbt run` and `dbt test` failures
* labeling and asking initial questions on created issues
* labeling and asking initial questions on created issues
- Add the `Workflow::Triage` label
- Add additional [labels](/handbook/business-ops/data-team/#issue-labeling)
- Assign it to the appropriate Manager, Data for prioritization
* guiding and responding to questions from GitLab Team-member
* maintaining the KPI Index page by creating an issue with any outstanding concerns (broken links, missing KPI definitions, charts vs links, etc) and assigning it to the appropriate stakeholders to correct as soon as possible.
 
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment