Who has got some good practice for managing Major Incidents?

On my desk if we get a major incident (say for instance  File Server down) - I will typically get many tickets all reporting the same issue. Ignoring the communications side of managing a major incident, how do you guys manage the actual tickets?

Each ticket logged needs a response and resolution to hit the SLA.

But that means I have to deal with each one as though its a standalone incident

I can link them all together to ensure the same notes go into each ticket, but that doesn't go close enough to what I want

When it comes to closure I have to close each one individually and add the correct closure codes etc.

Its very time consuming and detracts from resolving the actual issue.

In other tools I have used I would promote one incident ticket to be the master and make this ticket the SEV ONE Then I would link all the others to it, so that they will close when I close the main one. Get the same updates and the same emails.

The closest method I can see in SDP is linking them all to a problem ticket - but I refuse to manage Major Incidents in the Problem Management Module.

I attended the Manage Engine webinar about Major Incident Management some months back and whilst it was interesting and gave many tips about announcements it didn't really give way to manage 50 tickets which are all linked to the same major incident.

SO some tips on what you guys do, when suddenly you have 50 tickets all for a variation of the same thing.