There are cases where one user action causes multiple plugin events. This causes integrations like slack / hipchat and likely others to generate two independent events for a single logical action that the user took. For example:

• User update an issue + add a comment - this generates issue updated + note added independent events.

• User added a note + attached a file - from memory we don't have file updated event now, but if we do, we are likely to end up with two independent events.

We could approach this issue by:

1. Combine the two events into one - in this case an update event may include a note addition as well, for example. Though this may get tricky based on what events we are trying to combine.

2. Introduce a page shutdown event - hence, even though we may generate N events per page, we give the plugin a chance to potentially combine these as necessary as part of the shutdown event and take an action then. This may also defer processing of plugin code like we do with email.

Feels like option 2 may make sense given our recent changes.