Openbravo Issue Tracking System - Mantis @ OB |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000428 | Mantis @ OB | Others | public | 2008-05-26 12:16 | 2008-05-26 12:18 |
|
| Reporter | pjuvara | |
| Assigned To | | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | duplicate | |
| Platform | | OS | 20 | OS Version | Ubuntu 7.10 |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | No |
|
| Summary | 0000428: When issue severity is set to critical, priority should be set to immediate |
| Description | Developers should be responding to issues in order of priority.
In the normal worklflow, the priority should be set during scheduling but when a issue is log or upgraded to critical (meaning the users believe the product is non-functional), the priority should be set automatically to immediate to attract attention and trigger a fast response.
|
| Steps To Reproduce | |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | duplicate of | feature request | 0000299 | | closed | gorka_gil | Priority management |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2008-05-26 12:16 | pjuvara | New Issue | |
| 2008-05-26 12:17 | pjuvara | Status | new => closed |
| 2008-05-26 12:17 | pjuvara | Note Added: 0000332 | |
| 2008-05-26 12:17 | pjuvara | Duplicate ID | 0 => 299 |
| 2008-05-26 12:17 | pjuvara | Resolution | open => duplicate |
| 2008-05-26 12:18 | pjuvara | Relationship added | duplicate of 0000299 |