| Summary | When searching for alarms, filter by the maximum alarm value |
| Queue | Kronolith |
| Queue Version | Git master |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | chuck (at) horde (dot) org |
| Created | 10/16/2009 (5868 days ago) |
| Due | |
| Updated | 07/01/2011 (5245 days ago) |
| Assigned | |
| Resolved | 07/01/2011 (5245 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Rejected
really have so far in the future, but with an alarm set, that it's
worth filtering them out?
State ⇒ Accepted
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ When searching for alarms, filter by the maximum alarm value
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
and use that as a filter to ignore events that are far enough in the
future that they can't have an alarm set.