Comments
2 comments
-
Thanks for your kind words
You're correct in what the behaviour is. Incidents of the same type and subject on the same day go into the same group. This group is then open/closed/deleted as a whole.
There was some debate here about what the behaviour should be and our thinking was that we would keep the group together, primarily to avoid too much "spam" appearing with the same event happening over and over. So closing a group is "thanks - don't bother me again today"
However this beta is very much about hearing people's thoughts so please let us know what you think. -
Ok, I understand. I think my preference would be to have the option when closing the incident to explicitly indicate that future incidents in the same group should be ignored for the remainder of the day. My default, though, would probably be to be notified of future incidents in the same group because I'd expect them to often be unrelated to the earlier incidents.
Optionally, I could get by with specifying the behavio(u)r for each incident group. Blocking queries would go in the "treat subsequent incidents as new incidents" group. Low disk space might go in "remind me again tomorrow".
I do appreciate the effort to give us the control to limit the notifications, however.
Add comment
Please sign in to leave a comment.
I've noticed that when I close an incident, new occurrences of that incident type show up in "closed incidents" rather than open incidents. That was not what I expected since I was thinking I was closing the incident, not the incident group.
Will this only happen for new incidents of the same group on the same day as the incident that I closed?
Can you comment a little about what you were thinking would be a best practice regarding closing incidents? Should I not close them until the day after?