Need help ASAP to export history of all incidents of a particular assignment group to excel.

[varun42]

Hi

I need help to export history of all incidents of a particular group to csv or excel in one shot.

I am able to get the history of a single record(incident), but no option to export it to csv or excel,
only I am able to export it to PDF.which is in image format and not able to work with the data in it.

Not sure what is the right approach to export history of all incidents....can someone please direct me..?

Varun.

[john_andersen]

If this is a manual job you need to do quickly to analyze something it is easy to do:

1) Create the filter on the Incident List to get the items you are looking for
2) Right click the filter breadcrumbs and click "Copy URL"
3) Paste the URL in the browser address bar and append "&CSV" to the URL

A CSV file should be generated with all of the incidents that match the query.

If you have a lot of incidents, test this first with smaller queries to make sure it is not going to negatively affect other users on the instance.

[varun42]

Thanks for reply.

but I think you answered part of my question and overlooked the main.

Basically I need HISTORY of all incidents.For Example: who updated state and what are the old and new values of state.
I am able to get this for single incident, by selecting incident and in incident form right click->history-> list.
but not HISTORY OF ALL THE INCIDENTS TOGETHER at once.

Hope I made my point..:(

Varun

[jim pisello]

The sys_audit table records changes to auditable fields on records in the system. If you're looking for history, it's likely stored there. To get to the sys_audit table's list view, type sys_audit.list in the Type Filter Text field at the top of the Application Navigator, or append /sys_audit_list.do to the URL for your instance.

Once the list of audit records is displayed (it can take a while due to the large number of entries in that table) you can filter the list and export it to csv, Excel, etc.

[Mark Stanger]

This is all true. I would be EXTREMELY cautious when doing anything with sys_audit though. sys_audit is really designed just to show the history of a record within that record. Due to its size, it's going to be very slow and inefficient when accessed like this...to the point that it's possible to bring down an entire instance by doing so. The answer I would give to this question is that it just shouldn't be done. Instead, create a trend job, metric definition, or business rule to capture the specific, necessary information about incidents and store it in a smaller table that can be accessed (and exported) without bringing your whole instance down.