Comment 7 for bug 128174

@Amit: e-d-s is Evolution Data Server. What we normally call Evolution is actually a collection of sources and distribution packages (Evolution, Evolution Data Server, Evolution Exchange, the libraries, etc).

I do not have Feisty available for testing (in fact, I do have two servers running Feisty, but I am not going to install Evo there), so all I can do is verify if your problem is present in in up-to-date Evo. As I stated, it does not seem to -- per my initial understanding of your bug.

Rereading your last comment... it seems what you want is to: given a collection of triggered alarms, select a subset and close this subset; this action would then (implicitly) renew the rest of the collection for another round.

OTH Evolution seems to do it the other way: given a collection of triggered alarms, select a subset to be re-triggered; this action would then (implicitly) close the rest of the collection. This behaviour is similar to the one Lotus Notes uses.