You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Assignee: mhein
Status: Resolved (closed on 2011-11-16 16:11:20 +00:00)
Target Version: (none)
Last Update: 2011-11-16 16:11:20 +00:00 (in Redmine)
Default in Icinga-Classic is "fixed", Icinga-Web uses "flexible" downtimes per default. Choose on or the other, but please use the same defaults for both projects. I'd personally opt for "fixed" downtimes as they are easier to understand. People who understand the difference are also able to manually choose "flexible".
Another option would be a configuration option such as "default_downtime_type". If you evaluate this, please also have in mind what Icinga-Classic has done for #1642(#1676). And please reread my last comment in #1280 -> a quicktip explaining downtimes or a link pointing to the official documentation would be great.
The attached patch allows to have this configurable per Cronk, I'd still suggest to have the default set to "fixed" as it is in Icinga-Classic. Configuration can be done as follows once the patch is applied:
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2010
Created by tgelf on 2011-10-13 15:08:57 +00:00
Assignee: mhein
Status: Resolved (closed on 2011-11-16 16:11:20 +00:00)
Target Version: (none)
Last Update: 2011-11-16 16:11:20 +00:00 (in Redmine)
Default in Icinga-Classic is "fixed", Icinga-Web uses "flexible" downtimes per default. Choose on or the other, but please use the same defaults for both projects. I'd personally opt for "fixed" downtimes as they are easier to understand. People who understand the difference are also able to manually choose "flexible".
Attachments
Changesets
2011-11-16 15:33:59 +00:00 by mhein f114d55
2011-11-16 15:53:59 +00:00 by mhein fac28f6
The text was updated successfully, but these errors were encountered: