Handling class rejects
Revision as of 13:49, 20 January 2010 by MichaelWestwind (talk | contribs) (New page: ;Teachers: Fill out a class reject form outlining what the problem was and what you did to try and fix it (if anything). Take the box to Tech Support and put on the incoming shelf. ;Tec...)
- Teachers
Fill out a class reject form outlining what the problem was and what you did to try and fix it (if anything). Take the box to Tech Support and put on the incoming shelf.
- Tech Support
- Create an RT ticket for the box, putting the "Source" as "Class Reject".
- Evaluate the stated problem, making notes in the RT ticket. Fixing the problem is not necessary at this point.
- If the box is bootable, run a printme and put the general issue and the RT ticket number in the notes
- If the problem looks like something QC should have caught, flag the printme report and note that you did that in the RT ticket.
- Decide if the box is potentially fixable or not (if not sure, consider it fixable)
- Fixable boxes get taken to build with detailed notes on what was found. For now use the class reject form provided by the instructor (I am looking at creating a new form)
- If the box is unrepairable, put a "Rejected" sticker on it and take it to prebuild.