Triage Process

Triage Process

Triage query (vnext)

For every issue labeled Needs Triage we apply this process:

1. Is the issue unclear?
   • Need fundamental information?
     • @ mention the author and ask clarifying questions
       • Add Needs: Author Feedback label (these will return as Needs: Attention)
   • Needs clarification? needs PM design
   • Needs design work? needs dev design
2. Labels
   • vnext | .NET | WPF
   • Assign at least one Area (e.g. Area: Animation)
     • bug | proposal | question
   • Is this a partner request? Partner: AppConsult, Partner: Office, Partner: Stream, Partner: Xbox, or Partner: 3P (for all others)
   • Priority:
     • High (required for current milestone)? must-fix
     • Low? nice-to-have
     • Normal? no label
   • Other common labels:
     • Code Cleanup - code health issue
     • Documentation
     • Extensions - community modules
     • Needs WinUI 3 - cannot be accomplished with in-box XAML
     • API Completion - part of meeting the react-native API contract
   • Community interaction labels
     • Good First Task
     • help wanted
3. Milestone
   • All intended to be scheduled work should have a milestone. Not assigned to a milestone means low priority backlog.
4. Project
   • Assign to a project board if appropriate (grouped set of related work)
5. Assign
   • If someone should look at this immediately, in the next block of work (1-2 weeks), or they have the next action, assign to them
   • Leave unassigned to leave in the general poachable/backlog
6. Remove Needs Triage label

After processing Needs Triage, move on to Needs: Attention.

Bot Rules

• All new issues are labeled Needs Triage.
• If an issue with Needs: Author Feedback receives a comment from the author it changes to Needs: Attention.
• Issues without activity for 7 days with Needs: Author Feedback (or PRs with 'Changes Requested') receive a warning and are labeled no-recent-activity.
  • These will be closed after 14 days.
  • On any activity no-recent-activity is removed
• Issues labeled duplicate with no activity in 1 day receive a message and are closed.
• PRs labeled AutoMerge will be merged if all checks are met (minimum 60 minutes opened, squash merge, deletes branch).
• PRs are automatically labeled vnext or .NET depending on where the change is made.