Hallo Gero,

my first idea was the northbound interface, but I am not sure if assignment changes are included. The WS-Event Service might not support this:

NNMi supports WS-Eventing to allow client web-services to subscribe to incident events from NNMi. By subscribing to the NNMi notification service, the client receives Incidents as they are added to the NNMi Event pipeline. In addition, you can receive an update any time an Incident's lifecycleState or rcaState changes.

But reading further ... (so it might work on the "triggered" attribute in the text below):

Incident Subscription

NNMi notifies subscribers when new Incidents are created or when an Incident's lifecycleState or rcaActive is updated. Incident Correlations are also sent as notifications. New incidents and updates are sent as IncidentNotification messages and correlations appear as IncidentCorrelation messages (see the Incident service above for more details about this object). Some of the Incident attributes are designated with a "trigger". These are attributes that trigger another notification to be sent for the incident as NNMi changes these attributes values. The changed attribute values are included in the message. Additionally, a time stamp (see updateTime) and the previous values for these attributes are included when the update occurs. You can expect these previous values and the updateTime to be empty or null when the initial incident notification is received for a brand new incident.

(Source: Web Services APIs - Network Node Manager)

1. In the GUI I didn't see any timestamp for that

2. That is an incident config dump

3. see above

4. No incidents in OPTIC (yet)

HTH and best regards