Module: check_mk
Branch: master
Commit: 478561a802ac806c0371931a9b397f6a3dc8101f
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=478561a802ac80…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Thu Apr 7 16:51:23 2016 +0200
Updated bug entries #2485, #2486, #2487
---
.bugs/2485 | 9 +++++++++
.bugs/2486 | 9 +++++++++
.bugs/2487 | 10 ++++++++++
3 files changed, 28 insertions(+)
diff --git a/.bugs/2485 b/.bugs/2485
new file mode 100644
index 0000000..35bfb09
--- /dev/null
+++ b/.bugs/2485
@@ -0,0 +1,9 @@
+Title: statehist_annotation.mk must not be in var/check_mk/web
+Component: multisite
+State: open
+Date: 2016-04-07 13:32:15
+Targetversion: future
+Class: bug
+
+This is a name space conflict. A user with the name statehist_annotation.mk
+would conflict with this file!
diff --git a/.bugs/2486 b/.bugs/2486
new file mode 100644
index 0000000..e5f990f
--- /dev/null
+++ b/.bugs/2486
@@ -0,0 +1,9 @@
+Title: Availablity: visual levels do check themselves when working with annotations
+Component: multisite
+State: open
+Date: 2016-04-07 16:49:26
+Targetversion: 1.2.8
+Class: bug
+
+As ist seems if you edit annotations or stuff like that then suddenly the visual
+levels for availability are activated. Is this a name clash in an HTML variable?
diff --git a/.bugs/2487 b/.bugs/2487
new file mode 100644
index 0000000..775ec15
--- /dev/null
+++ b/.bugs/2487
@@ -0,0 +1,10 @@
+Title: Availability: Changing time range of an annotation duplicates it
+Component: multisite
+State: open
+Date: 2016-04-07 16:50:29
+Targetversion: 1.2.8
+Class: bug
+
+The start/end is used as a key. If you edit an existing annotation and
+change one of those - Check_MK thinks you are creating a new one and
+creates a duplicate entry.