Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0000428 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| feature request | [Mantis @ OB] Others | minor | have not tried | 2008-05-26 12:16 | 2008-05-26 12:18 | |||
| Reporter | pjuvara | View Status | public | |||||
| Assigned To | ||||||||
| Priority | normal | Resolution | duplicate | |||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | |||||
| OS | Linux 32 bit | Database | Oracle | Java version | 1.6 | |||
| OS Version | Ubuntu 7.10 | Database version | 10g | Ant version | 1.5 | |||
| Review Assigned To | ||||||||
| 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. | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
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 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |