S&E Automated Triage Rules
This is a living document and will change as active team/theme development moves through the system. If you notice that things are out of date, please update as needed. If you're unsure, leave a comment with a question! Thanks 
Summary
This page is meant to document the automation rules for incoming bugs being reported and how to minimize feedback loops where possible. Additional context on components can be viewed with the full listing of Platform Areas and Product Components.
Engagement Theme
Automation Rules
| Platform Area | Product Component(s) | Automation | Squad Details |
|---|---|---|---|
| Catalog & Publishing | Course About Page, | CR
Eng Ticket
| Website Squad Eng Lead: Albemarle (Deactivated) Product Lead: Gerrit Orem (Deactivated) |
| Catalog & Publishing | Course Publishing Workflow | CR
Eng Ticket
| Publisher Squad Eng Lead: Jason Myatt (Deactivated) |
Programs Theme
Automation Rules
/wiki/spaces/PROD/pages/933200139
| Platform Area | Product Component | Automation | Squad Details |
|---|---|---|---|
| Content & Authoring | Content and Authoring: | CR
Eng Ticket
| Master's & MicroMasters Squad Eng Lead: Mat Carter (Deactivated) Product Lead: Deen Abdul-Hathi (Deactivated) |
| Learner Experience | Master Track | CR
Eng Ticket
| Master's & MicroMasters Squad Eng Lead: Simon Chen Product Lead: Deen Abdul-Hathi (Deactivated) |
Platform Theme
Automation Rules
| Platform Area | Product Component | Automation | Squad Details |
|---|---|---|---|
edX for Business Theme
Automation Rules
| Platform Area | Product Component | Automation | Squad Details |
|---|---|---|---|
| Business & Enterprise | *any | CR
Eng Ticket
| * S&E team looks at these tickets in the queue to check if they are Ent specific or more broad in scope |