| | 1 | == Main priority == |
| | 2 | |
| | 3 | Critical:: |
| | 4 | Something that is needed now at least a work round. Typically showstopper bugs on production |
| | 5 | Urgent:: |
| | 6 | Typically data fixes needed by next day and code fix needed in next release or as per detailed priority. |
| | 7 | High:: |
| | 8 | Important bugs and CRs to be looked into as per detailed priority. |
| | 9 | Medium:: |
| | 10 | Bugs and CR with medium priority |
| | 11 | Low:: |
| | 12 | Not so important but should be done sometime |
| | 13 | |
| | 14 | == Detailed priority == |
| | 15 | |
| | 16 | 1:: |
| | 17 | Defect stops user saving transactions, creates bad data on database, pagination errors, user allowed to enter data for which they do not have permission, approvals not working |
| | 18 | 2:: |
| | 19 | Annoying UI defects that don't stop users entering and saving transactions, eg buttons do not work |
| | 20 | 3:: |
| | 21 | Defects in external Prints - RFQ, PO, FA, SIWB and internal prints that are key to audit process - CBA, PI, GRN |
| | 22 | 4:: |
| | 23 | Defects in internal Prints - RO, SP - and management reports |
| | 24 | 5:: |
| | 25 | Defects in import/export |
| | 26 | 6:: |
| | 27 | Defects related to performance |
| | 28 | 7:: |
| | 29 | Design defects - functional flaws, loopholes that allow users to enter wrong data |
