Possible goals

• try and find metrics for the numbers of ISEs people are getting and highlight very common ones. Group them by module/area if possible.
• work backwards from most common ones to try and link these ISEs to existing tickets or file new bugs

This may or may not be a useful idea; I'll let the developers decide. My own personal experience is sometimes that a top down "try and reproduce an issue via UI" can /sometimes/ be less effective than a bottom-up approach "here's the most common stack trace; how can the code get itself into this position?"