Lead Issue Review (Tech Stack Old vs New)

[ryanfchase]

Overview

This ticket will contain instructions for leads to review issues that...

• they are assigned to
• they have created
• they think is relevant to their team (e.g. Engineering Lead will review issues that have the label role: frontend or role: backend)

Action Items

All open issues are labeled Tech Stack: Missing. For each issue...

• remove Tech Stack: Missing, indicating that this ticket has been reviewed
• perform one of the three...
  • add Tech Stack: Old if this issue was only pertinent to the AWS backend
  • add Tech Stack: New if the issue remains relevant and actionable, despite the tech stack change
  • if none of the above apply, we should Close as unplanned, pruning this issue from our board
• assign yourself to this ticket and comment down any useful information (e.g. if issues were modified to remain relevant, jot down which issue and what changed)

1. Check the box when this process is complete for your team

• Engineering
• UI/UX Design
• Research
• Product Management

2. After all leads have reviewed their issues:

• close all tickets with the label Tech Stack: Missing
• remove label Tech Stack: New, no need for this designation
• give a new name for Tech Stack: Old to something more informative (suggestions welcome)

ENGINEERING ONLY:

• close all Pull Requests

[hworthen]

UX research issues are updated

[ryanfchase]

Engineering issues are cleaned out

[ryanfchase]

Closing this issue as done. All team leads have closed all relevant issues.