mantisbt:issue:7721
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mantisbt:issue:7721 [2010/12/06 05:20] – Update for a new interest in ITIL v3 ! jeank6 | mantisbt:issue:7721 [2015/09/13 02:57] (current) – [Request Tracker] vboctor | ||
---|---|---|---|
Line 53: | Line 53: | ||
===== Plugins & scripts related ===== | ===== Plugins & scripts related ===== | ||
TODO: Add other links | TODO: Add other links | ||
+ | |||
+ | Apparently, you might consider submitting a Git repository with your plugin to https:// | ||
==== Solution for reporting via E-Mail ==== | ==== Solution for reporting via E-Mail ==== | ||
Line 67: | Line 69: | ||
* Last update: 2010-09-24 01:29 | * Last update: 2010-09-24 01:29 | ||
* TODO: Contact [[http:// | * TODO: Contact [[http:// | ||
+ | |||
+ | ==== Automatic reminders based upon Status/Due date ==== | ||
+ | It's a script for sending reminders to developers to be informed about forthcoming Due dates. | ||
+ | * Site: [[http:// | ||
+ | * Author: Cas | ||
+ | * Last update: 2010-05-07 03:53 | ||
+ | |||
+ | ===== Key concept ===== | ||
+ | ==== ITIL Incident | ||
+ | It's a very interesting concept for an easy classification of an incident | ||
+ | * Incident | ||
+ | Any event which is not part of the standard operation of a IT service and which causes, or may cause, an interruption to, or a reduction in the quality of that service. (in ITIL v3 Service Request are not Incident, but Service Request | ||
+ | |||
+ | * Impact | ||
+ | Impact describes the measure of the business criticality of an incident. Impact is often based on the extent to which an incident leads to distortion of agreed or expected Service Levels. (Ie: loss of revenue, loss of business reputation, breach of legal constraints, | ||
+ | |||
+ | * Urgency | ||
+ | Measure of the business criticality of an incident or problem based on the business needs of the customer. Urgency is the speed required for the resolution | ||
+ | |||
+ | * Priority | ||
+ | Priority is the sequence in which an incident or problem needs to be resolved, based on impact and urgency. And it serves to identify an acceptable period for the implementation of an action | ||
+ | |||
+ | < | ||
+ | +--------+------+------+------+------+ | ||
+ | | | ||
+ | + | ||
+ | | | ||
+ | +--------+------+------+------+------+ | ||
+ | | |High | 1 | ||
+ | + +------+------+------+------+ | ||
+ | |Urgency |Medium| | ||
+ | + +------+------+------+------+ | ||
+ | | |Low | ||
+ | +--------+------+------+------+------+ | ||
+ | </ | ||
+ | TODO: convert to table : http:// | ||
===== See also ===== | ===== See also ===== | ||
Line 73: | Line 111: | ||
TODO: Add other links towards another open source tool could be a good solution | TODO: Add other links towards another open source tool could be a good solution | ||
- | ==== GLPI ==== | ||
- | GLPI, an initialism for Gestionnaire libre de parc informatique (Free Management of Computer Equipment), is a free trouble ticket system software that anyone can use to build up a database with an inventory for computer equipment (computers, software, printers, etc.). | ||
- | * Site: [[http:// | ||
- | ==== External links ==== | ||
- | http:// | ||
+ | |||
+ | ==== External links ==== | ||
+ | * http:// | ||
+ | * http:// | ||
===== Acknowledgement ===== | ===== Acknowledgement ===== | ||
This feature was initiated by dsolajic & vboctor ([[http:// | This feature was initiated by dsolajic & vboctor ([[http:// |
mantisbt/issue/7721.1291630813.txt.gz · Last modified: 2010/12/06 06:27 (external edit)