DWSD.md

Field Issue Triage

type
interaction
interaction-type
review
for-domain
Charger ART
interaction-of
Charger ART Board › Field Issue › Triage , Field Issue Route › issue @ Train , Field Service
start
2026-09-29T09:00:00
end
2026-09-29T09:30:00
rrule
RRULE:FREQ=WEEKLY;BYDAY=TU
created_at
2026-10-10

Purpose

Thirty minutes every Tuesday: Mateo Ruiz brings the week’s Field Issues from Field Service, the two product owners (Lukas Weber, Sofia Marques) and Ravi Anand from Connectivity sit with him, and the group starts from the list the Field Issue Triage Agent has clustered and ranked overnight. For each issue one call: hotfix — safety or a fleet down, into the expedite lane now — or feature, into the program backlog for the next PI planning. That call is the fork in the Field Issue Route, and this is where it is made.

Field Service is not in the ART; this half hour is its door into the train.

Modeling note

Anchored three ways: on the Triage column of the expedite lane, on the route’s issue @ Train stage, and on Field Service itself — a plain team with no board, so the marker sits on its box in the units view.

Like what you see? → Start — build your own org folder in ~2 min

Field Issue Triage.md
---
type: interaction
interaction-type: review
for-domain: "[[Charger ART]]"
interaction-of:
  - "[[Charger ART Board]]#Charger ART/lane:Field Issue/col:Triage::in"
  - "[[Field Issue Route]]/stage:issue @ Train::in"
  - "[[Field Service]]"
start: 2026-09-29T09:00:00
end: 2026-09-29T09:30:00
rrule: RRULE:FREQ=WEEKLY;BYDAY=TU
created_at: 2026-10-10
---
## Purpose


Thirty minutes every Tuesday: [[Mateo Ruiz]] brings the week's [[Field Issue]]s from
[[Field Service]], the two product owners ([[Lukas Weber]], [[Sofia Marques]]) and
[[Ravi Anand]] from [[Connectivity]] sit with him, and the group starts from the list the
[[Field Issue Triage Agent]] has clustered and ranked overnight. For each issue one call:
**hotfix** — safety or a fleet down, into the expedite lane now — or **feature**, into the
program backlog for the next PI planning. That call is the fork in the
[[Field Issue Route]], and this is where it is made.


[[Field Service]] is not in the ART; this half hour is its door into the train.


> [!NOTE]
> **Modeling note.** Anchored three ways: on the `Triage` column of the expedite lane, on
> the route's `issue @ Train` stage, and on [[Field Service]] itself — a plain team with no
> board, so the marker sits on its box in the units view.