Triage Process

Goals

What are our goals for triaging incoming issues?

1. Groom a backlog of actionable issues
2. Engage with the community and respond to feedback
3. Make connections between efforts/engineers
4. Grow knowledge that spans the entire product (bring teams together) and related products (macOS etc.)

We also do our best to align with issue management practices from Facebook's react-native repo (and we participate in both) so that people have a consistent experience moving between RN and RNW.

Assignee

If an issue is assigned to someone it is assumed that that person is currently working on that issue, they plan to in the next couple weeks, or they have the next "action" on that issue.

Contact the current assignee before working on an issue to prevent duplicated effort. If you are no longer working on one of your assigned issues you should unassign yourself (leave a note so that the next person can pick up where you left off).

To find issues assigned to you across all your github repros you can visit here.

Triage Process

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
   • 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
   • Legacy implementation? .NET | WPF
   • Community interaction labels
     • Good First Task
     • help wanted
3. Milestone
   • All triaged issues should be assigned a milestone. If the work is not scheduled then assign the Backlog milestone.
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

Triage order

1. Needs Triage
2. Needs Attention.
3. Samples repo Needs Triage
4. Samples repo Needs Attention
5. Open PRs
6. TBD: add links to community modules

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.
• Issues labeled Needs: Environment Info will get a response with steps for how to add environment information and will be labeled Needs: Author Feedback.
• Issues labeled Needs: Verify on Latest Version will get a response with information on version compatibility and will be labeled Needs: Author Feedback.
• Issues labeled Resolution: For Stack Overflow will get a response with a redirection link and will be 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.