How to handle stateless incidents

[hmpf]

Stateless incidents (end_time == null) look too much like stateful incidents (end_time != null). There's no controls for showing/hiding stateless incidents. They are visible in the incident-list if "Both" is on for both acked and openness. In the detail-box, they lack duration, but there's nothing else that marks it as stateless. They currently have a start event, this is probably not a good idea.

A stateless incident logically doesn't really have a start time or end time, just a timestamp. We just reuse the start_time-field to hold the value.

See also Uninett/Argus#206.

[hmpf]

Copied from Uninett/Argus#206 (comment):

@lunkwill42 said:

Since we do not currently have a filter to turn on/off stateless incidents, it's okay to show them when the "open/closed" filter is chosen. However, the red "Closed" badge makes no sense on these incidents - and neither does the green "Open" badge. The badge should either be entirely removed, or perhaps replaced with "Stateless" or "Instant".

[hmpf]

.. maybe they should have a "stateless"-event instead of a start-event..