Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0010270 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| feature request | [Contribution Requests] Sponsored Development | major | have not tried | 2009-08-13 19:03 | 2011-02-04 09:12 | |||||||
| Reporter | pjuvara | View Status | public | |||||||||
| Assigned To | rmorley | |||||||||||
| Priority | normal | Resolution | open | |||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | |||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Review Assigned To | ||||||||||||
| Summary | 0010270: Machine incidences registration | |||||||||||
| Description | In order to keep track of all incidents that happen for a specific machine, it would be great if this could be registered in the ERP. Each incident would also have a life cycle that would go through different statuses (pending, solved, working, etc.). The incident would also affect to the availability of the machine. Depending on the severity, the machine could be off or partially available. | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-08-13 19:03 | pjuvara | New Issue | |
| 2009-08-13 19:03 | pjuvara | Assigned To | => pjuvara |
| 2011-02-04 09:12 | jpabloae | Assigned To | pjuvara => rmorley |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |