The Jobs table does not contain any history of how an event record has been changed. It also does not contain a history of events which have been abandoned after an incident has been reassociated.
When an incident is first created within NMS, the application creates an event for it. If that incident is grouped into another event, the original Event IDX is no longer stored within the Jobs Table. Since the Jobs table has no history (birth/death columns) there is no way to determine when an event was generated and when it was abandoned.
The Jobs table contains many fields which are tracked in other tables. There are some fields however which are not tracked which can potentially change. This includes the lead call details (external_id, alias, customer details).
NMS should have a Job Change Log, similiar in functionality to the Incident change log. The log would capture job details before a change is made (act as a “dead” record for the job record). The record should contain/track Event IDX, Event CLS, Lead Call details (External_ID, Customer details) and the Numb field for each record. It should also track if an event has been abandoned because the original incident associated to it was grouped to a different event. The log should also track if the Numb value has changed for an Event record.