• Check what exist and you may pick-up some in this list of published extensions and install them as documented.

Helper to create the mandatory files for a new extension.

If you have never done it:

• Refer to iTop customization mechanism to understand how to extend or modify iTop.
• Start by this step by step example, to create your first extension.
• Check iTop coding standards
• Always refer to XML Data Model Reference and XML Portal reference for XML evolutions and exact syntax.
• If you have a doubt about the sequence of PHP methods on object manipulation: CRUD methods sequentiallity
• For writing generic extensions, limiting risks of incompatibilities with other extensions, uses the extensions API.

• Add a field to the Server class
• Define your own dictionary entries - Added in July 2019
• Force a field to be always mandatory - Added in July 2019
• Remove a field from Ticket - Added in August 2019
• Add a Dashboard on a Team - New in 2.6 - added in July 2019
• Creating a new class of CI: Monitor
• Define a dependency - added in July 2021

• Flag Tickets waiting for a 3rd party - Added in July 2019
  • Count time spent in a state
  • Behavior of a Stopwatch
• Force a field to be mandatory by lifecycle - Added in July 2019
• Add a lifecycle on Physical Device - Added in August 2019

• Define Obsolescence rules - New in 2.4
• Prevent duplicates - New in 2.6 - added in July 2019

• Create new Profile
• Delegate 'Admin tools' menus - New in 2.5
• Define your own Password policy - New in 2.7
• Implement Password expiration - New in 2.7
• Create your authentication method - New in 2.7

• Copy linkedset with object copier - Added in Dec 2019
• Compute WorkOrder End Date - Added in August 2019
• Update a counter on CustomerContract with count of closed Tickets
• Count Ticket reopening - Added in July 2019
• Calculated field & Cascading update - Added in June 2018
• Sum Components cost on Contract - Added in June 2020
• Store Count of n:n relation - Added in August 2020
• Synchronize data from an external application - Added in October 2020

• Change the iTop Homepage - Added in July 2020
• Force a field to be mandatory - Added in July 2019
• Force a field to be read only - Added in August 2019
• Form Prefill - New in 2.5
• Check data integrity: Ensure that End date on a Change is after Start date - Added in July 2019
• Hide cost for some users - Added in July 2019
• Add entry in ''other actions'' popup menu
• Creating a new dashlet for console dashboards: iFrame
• Enrich display of an object - Added in July 2019
• Highlight critical objects - New in 2.7
• Change Console colors - New in 2.7
• Highlight state for some values - New in 2.7
• Change menu icon - New in 3.0

• Get resolution delay taking coverage window into account - Added in July 2019
• Count the number of time a UserRequest is re-open - Added in July 2019
  • Desactivate history tracking on the counter
• Close automatically after a delay - Added in July 2020
• User Request where TTO start on a planned date - Added in July 2019
• Planned User Request (advanced) - Added in July 2019
• SLA by Service Subcategory - Added in August 2019
• Inherite services from parent organization - Added in August 2019
• Use an holiday calendar per country for SLA computation
• Automatically redispatch Ticket to above team when reaching 75% of TTR.
• Cascading Change closure: Resolve automatically all associated User Requests on Related change closure

Only available since version 2.3, the enhanced Portal offers customization options

• Portal Customization Overview
• Portal XML Reference
• Portal Limitations

Examples of How to :

• Make a field mandatory on the User Portal - Added in July 2019
• Allow to see more or less Tickets - Added in August 2019
• Create Tickets for others - Added in July 2021
• Change scopes
• Change the bootstrap theme
• Change a brick icon
• Add a "create" button
• Add a new browse mode
• Add a Dashlet (since 2.5)
• Create a new portal - Added January 2021

• How to translate