clarencen/lshift — Issue #322: Heat map should should be organized by detection date
Author: clarencen
Created: 2011-11-14 22:42:31+00:00
State: open

At the moment the events in the heat map are arranged by business date. It is probably a better idea to order these by the date that the conflicts occur. For example, if a single error occurs that causes a bunch of entities to conflict, some of these entities could have business dates that are far apart from each other. It would be more intuitive to have these clustered on the point in time that the error occurred - ordering by business date would stretch the heat map in an unintuitive way.

This means a change in the back end and the front end:

* The session manager should timestamp events as they go into the pending state
* This timestamp needs to go into the session event
* The UI needs to group by this timestamp rather than the business date, which is due to be deprecated as a first class attribute (see ticket #2)