Combodo/iTop 3.3.0-beta1 on GitHub

For iTop discovery

Localized sample data

Sample data can now be installed in English, French or German. On first installation, iTop relies on the selected default language (not the administrator's own language) to load structural and sample data. Only French and German are available so far, in addition to English, which remains the default.

More samples

More sample data on Services, Contracts, SLAs and SLTs
More sample data on Organizations and Persons
Sample users are created automatically so you can test what each profile sees and can do. For security reasons they are disabled by default, with an expired password, and must be activated explicitly.

For users

Container Management (optional module)

A new module that adds:

a Cloud class attached to Virtualization
several containerization classes: ContainerImage, ContainerApplication, ContainerCluster, ContainerHost

Data Flow Management (optional module)

A new module introducing the DataFlow class:

models a flow between two FunctionalCIs, with a frequency, a flow type, a criticality, etc.
being a FunctionalCI itself, it can be linked to a Ticket and taken into account in impact analyses
by default the source impacts the flow, and by default the flow does not impact its destination
on top of the standard impact analyses, two map views are available: Outbound flows (flows leaving a given CI) and Inbound flows (flows reaching it)

The computation is recursive: when a flow reaches another CI, iTop also computes that CI's flows and displays them on the same graph. Loops can therefore appear — an outbound flow coming back as an inbound flow on the original CI — and the same applies in the inbound direction.

CMDB presentation

The CMDB dashboard displays class badges with tooltips explaining the purpose of each class within iTop.
It now includes classes that were previously missing: Software, OS Family, OS Version, IOS Version, Tape, NAS file system and Fiber Channel Interface.

Display of a CI

The display of all CMDB objects has been harmonized around a single standard: two columns (col:col1 / col:col2) and four or five fieldsets.

Fieldset	Column	Fields it contains (in this order, where they exist on the class)
General information	First	Name, Organization, Status, Business criticality, Location, Rack, Enclosure
xxxxx specifics	First	all fields that do not belong to any other fieldset
Dates	Second	all date-related fields: move to production, purchase, end of warranty, end of support, etc.
Power supply	Second	datacenter devices only (PowerA and PowerB source fields)
Description	Second	comment or description, logo, and the groups the CI belongs to

Groups usage

The existing Group class was barely visible and therefore rarely used. It is now exposed as a tagset field on every CI, making it easy to tag CIs for any grouping purpose: critical or test environments, project scope, items to be upgraded, and so on.

End of Support

End-of-support information can now be managed at Model and Software level, and is displayed on every associated CI — useful for checking whether your infrastructure is at risk because hardware or software is out of support.

Highlighting status with colors

Every CI status value now uses a background color, making it easier to tell production apart from implementation, stock and inactive items.

Impact analysis and logos

The impact analysis feature is now much more visible on object views.
Logos are no longer generic: they can be defined dynamically per category, per software or per object instance, which makes impact graphs far easier to read.
- among Network Devices, firewalls, routers, switches and load balancers each get a distinct icon based on their type
- Application Solution, Business Process, Software and OS Family accept a different logo per instance

Service Management

The Service Management menu has been restructured, with tooltips on menu entries.
A new Service Catalog dashboard has been added.
Contract statuses now use the standard set of state colors.
Services, Service Subcategories and Contracts in obsolete status are hidden from users who chose to hide obsolete objects in their user preferences.
Service and Service Subcategory status is now mandatory, defaulting to implementation. This eases reporting and lets you prepare future subcategories without affecting customers already buying the corresponding service.

Ticketing

Colors

Incidents and Requests are color-coded in full ITIL mode
Priority values are also color-coded in full ITIL mode

Menu labels

FR and EN menu labels and tooltips have been harmonized across User Request, Incident and Change

tto and ttr timespent fields
These two stopwatch sub-items now exist out of the box, with no datamodel customization required.

They only hold a value when their associated stopwatch (tto or ttr) is not running
They represent time spent during working hours, excluding holidays, before the ticket was owned (tto) or resolved (ttr)
Time spent in statuses excluded from those stopwatches (such as pending) is not counted
Not to be confused with the long-standing Resolution delay field (time_spent), which is unrelated to stopwatches: it counts from the ticket's start_date (its creation in iTop) to its resolution_date, regardless of holidays or coverage windows

Request type behavior

In full ITIL mode, this field has been removed from the User Request display, where it served no purpose
In simple ticket mode:
- Service subcategory selection is no longer restricted by this field — both incident and request subcategories are offered
- on submission, if the request type conflicts with the selected service subcategory, the subcategory wins and the request type is corrected automatically

Team tickets list
The tickets_list field, hidden because of performance issues, has been replaced by a dashboard attribute restricted to open tickets and loaded only when the tab is opened.

Case log entries copied from the parent
When an entry is added to a ticket's case log, it is copied automatically to all child tickets, with a prefix identifying its origin:

in the private log, the prefix includes a link back to the parent ticket
in the public log, no hyperlink is added, since that log is visible in the User Portal where a back-office link would appear broken

Incident parent request

The Incident class gains a parent_request_id external key pointing to a UserRequest
The UserRequest class gains a matching "Sub-Incidents" tab

User Portal

New look

The new portal look, previously offered as an extension for iTop 3.2, is now fully integrated and replaces the old look and feel.

Other changes

On a ticket, the attachments list has moved above the case log, so it stays visible on tickets with long discussions.
Services and Service Subcategories in implementation status are no longer visible in the portal, allowing you to prepare future offerings before exposing them to customers.

For administrators

Setup and upgrade

It is now possible to uninstall some extensions. As a result:

the setup and upgrade mechanisms have been heavily reworked
the wizard pages differ slightly from before (new installation wizard, new update wizard)
a new Extension management page in the back office lets administrators and superusers assess whether an extension can be removed safely

Notification on attachments

Two new triggers fire when an attachment is added to or deleted from an object. The attachment file itself can be included in the notification email.

Configuration: shortcut actions

Selected object actions can be pulled out of the actions drop-down menu and displayed as icons, via the shortcut_actions setting.

General example:

'shortcut_actions' => 'UI:Menu:Modify,UI:Menu:New, UI:Menu:OpenOQL,UI:Menu:CSVExport ,UI:Menu:EMail,UI:Menu:Delete,UI:Menu:PrintableVersion,UI:Menu:ExportXLSX,UI:Menu:ExportPDF',

Impact analyses:

'shortcut_actions' => 'UI:Menu:Modify,UI:Menu:New,UI:Menu:impacts_down,UI:Menu:impacts_up',

Add me to contact:

'shortcut_actions' => 'UI:Menu:Modify,UI:Menu:New,UI:Menu:AddMeToContact',

Audit Rule

Two new fields on Audit Rules: the corrective process to apply and the contact responsible for the rule. Rules become self-explanatory, which improves audit quality.

OQL Query

Two new fields on OQL Queries: their usages and a responsible contact. This makes large query libraries easier to manage through filtering criteria rather than a naming convention alone.

Super User rights

Rights that were missing from the Super User profile have been added, including:

transitions on Incidents in full ITIL mode
transitions on Work Orders
transitions on Customer Surveys
default actions provided by the User Action Configurator
transitions on Global Requests
collectors and data synchro

For developers

This section appears in the page's table of contents but has no published content yet; refer to the migration notes intended for extension developers.

Source: official iTop documentation — "What's new in iTop 3.3" (itophub.io), last modified 2026/07/23.