This extension gives you the opportunity to combine an issue tracker like RT with an IT documentation tool / CMDB like i-doit.
It uses i-doit's API to relate a ticket with one or more CIs / objects managed by i-doit.
On i-doit's side you are able to view all tickets related to an object.
This extension also supports i-doit's multi-mandator functionality.

i-doit ("I document IT") is a web-based tool to document complex IT infrastructures.
It provides several modules like a ITIL compliant Configuration Management Database (CMDB).
More information about i-doit is available under http://www.i-doit.org/.
Its core is Free and Open Source Software.
Visit http://www.i-doit.com/ for commercial support and additional services.
Please note,
that i-doit's API (which is essential for this extension) is currently only implemented in the commercial branch.

Please be aware of browsers' "Same Origin Policy"! This extension uses AJAX requests access i-doit's API. If RT and i-doit are not available under the same domain name (or IP address), AJAX calls will fail.

To avoid this "problem" (actually this policy is very useful) you can setup an AJAX proxy. This extension already provides such a proxy located under etc/. It's written in PHP, so you have to install PHP 5.2 or higher and the PHP extension curl on the same machine where RT is installed. Make this little script available through your web server and edit the script by setting $l_url to the URL of i-doit's API, e. g. http://example.org/i-doit/index.php?api=jsonrpc. In RT's site configuration $IDoitAPI has to be set to this script, e. g. http://rt.example.org/path/to/i-doit_api_proxy.php.

You need the identifier of a mandator who owns the objects, but this may also be set while creating a ticket. This identifier has be to added to the list of the corresponding custom field. For a list of (activated) mandators and their identifiers see i-doit's admin center.

Sometimes it's better to "clean up" the web user interface. Whenever you only have 1 mandator within i-doit and don't want to edit the object identifiers manually it's recommended to hide the used custom fields.

After all your new configuration will take effect after restarting your RT environment:

rm -rf $RT_HOME/var/mason_data/obj/* && service apache2 restart

This is an example for deleting the mason cache and restarting the Apache HTTP web server on a Debian GNU/Linux based operating system.

Whenever you create a new ticket or edit an existing one you are able to reference this ticket with one or more objects in i-doit. An additional box with the so-called "object browser" will shown up. Just select the objects you need or unselect the objects you don't need.