User Tools

Site Tools


This is an old revision of the document!

ITIL compliance for Mantis

nit : this is a second structure for this topic. Feel free to enrich & modify the following approach

The Information Technology Infrastructure Library (ITIL) is a set of concepts and best practices for Information Technology Services Management (ITSM), Information Technology (IT) development and IT operations.

ITIL gives detailed descriptions of a number of important IT practices and provides comprehensive checklists, tasks and procedures that any IT organization can tailor to its needs.

ISO/IEC 20000, like its BS 15000 predecessor, was originally developed to reflect best practice guidance contained within the ITIL framework

ITIL v3 is set of best practices (guidelines) for IT Management. It can be devided in 2 main areas:

  • Service Delivery (oriented toward customers)
  1. Service Level Management,
  2. Availability Management,
  3. IT Continuity Management,
  4. Capacity Management,
  5. Security Management and IT Financial Management
  • Service Support
  1. Incident Management
  2. Problem Management
  3. Change Management
  4. Release Management
  5. Configuration Management.

The oportunity is more in Service Support area plus Service Level Management. The different subject to cover are the following :

  • Adjusting terminology to ITIL

This part is pure mantis configuration. Maybe sharing configuration is enough ?

For dsolajic : bug → incident, severity → impact, urgency → priority (actualy urgency and impact give priority through Eisenhower matrix)) Priorities are usualy fixed on low, medium and high.

For nit : reproducibility → Nature (incident, service request, request for change), severity→impact (low, high), priority→urgency (urgent, not urgent), priority = low, medium and high quite the same in fact

  • Defining Service Level Agreement (response, resolution times for incidents, service hours, service window, working/non working days, holidays, …)

Alerts on incidents close to resolution time, etc. AND Configurable reporting

  1. a data structure (made of global variable or of a database table) to determine what is a working day (holidays, service window).
  2. a data structure to determine your SLR. Each row of SLR can be seen as a set of 2 whereclauses. 1st for number of issue really treated, 2nd for number of issue to treat.
  3. a data structure to determine your SLA. Each row of SLA can be seen as a periodicity and a whereclause (number of issue to be treated regarding the Agreement)
  • Configuration Management DataBase (CMDB) with Configuration Items (hardware, software (description), documents, specifications, etc.)

Solution for reporting via E-Mail Using mail Parser provided here ? ?

  • Defining workflow of the incident (that I would say already exists in Mantis)

See also

Mantis is not very oriented to that topic. Maybe a link towards another open source tool could be a good solution. (example : )

  • E-mail interface so the client can add an issue through e-mail


This feature was initiated by dsolajic & vboctor (7721).

mantisbt/issue/7721.1291628473.txt.gz · Last modified: 2010/12/06 05:20 (external edit)