Module: check_mk
Branch: master
Commit: e6c8bc06eb29e2c4e919f381e8d26fb4f12e6898
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=e6c8bc06eb29e2…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Wed Aug 22 11:28:15 2012 +0200
Add new bug entries for some old nastinesses
---
.bugs/797 | 11 +++++++++++
.bugs/798 | 15 +++++++++++++++
2 files changed, 26 insertions(+), 0 deletions(-)
diff --git a/.bugs/797 b/.bugs/797
new file mode 100644
index 0000000..3e7099e
--- /dev/null
+++ b/.bugs/797
@@ -0,0 +1,11 @@
+Title: PNP Graph zoom zooms wrong position
+Component: multisite
+State: open
+Date: 2012-08-22 11:21:24
+Targetversion: 1.2.0
+Class: bug
+
+If you make a area selection on a pnp graphs displayed in multisite you end up
+at a different position in the graph than you expected
+If you try to view the right-most position, it will not be possible because you
+always get something else.
diff --git a/.bugs/798 b/.bugs/798
new file mode 100644
index 0000000..c98b677
--- /dev/null
+++ b/.bugs/798
@@ -0,0 +1,15 @@
+Title: PNP graphs and localtime
+Component: multisite
+State: open
+Date: 2012-08-22 11:23:13
+Targetversion: future
+Class: nastiness
+
+If the user and the monitoring server exist in different timezones, multisi
+has enough smarts to handle this. the problem is with PNP graphs - if the
+user views them, he ends up with time information recorded on the nagios server
+This breaks the UI logic, and worse, he can't even tell what timezone the server
+is running in.
+It might be possible to fudge with the numbers when calling PNP.
+Otherwise we could at least add timezone info to the output, but this would
+only work if there's just a single monitoring host (thus useless)
Module: check_mk
Branch: master
Commit: a1e3c3e945e4835939712c0e027f676485ab94c6
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=a1e3c3e945e483…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Tue Aug 21 17:29:37 2012 +0200
Add new bug entry
---
.bugs/726 | 20 ++++++++++++++++++++
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/.bugs/726 b/.bugs/726
new file mode 100644
index 0000000..28b5824
--- /dev/null
+++ b/.bugs/726
@@ -0,0 +1,20 @@
+Title: WATO Users & Contacts misses sorting
+Component: wato
+State: open
+Date: 2012-08-21 17:26:38
+Targetversion: 1.2.0
+Class: cleanup
+
+The users & contacts page seems to not sort the displayed users alphabetically
+(or by any other visible pattern)
+
+It should offer some sorting, we have users with 800+ live contacts in there.
+And it's not practical with many less.
+
+Example order:
+list all admin accounts
+list all user accounts
+list all guest accounts
+
+oh, that seems like saying "list be role" - yes, maybe.
+per group they should really be sorted a-z
Module: check_mk
Branch: master
Commit: 9c553f6765ac958500490bd37463f097641d0793
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=9c553f6765ac95…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Tue Aug 21 16:44:50 2012 +0200
Add new bug entry
---
.bugs/725 | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/.bugs/725 b/.bugs/725
new file mode 100644
index 0000000..afb6324
--- /dev/null
+++ b/.bugs/725
@@ -0,0 +1,11 @@
+Title: parent scan might want to exclude dyndns_hosts
+Component: core
+State: open
+Date: 2012-08-21 16:43:10
+Targetversion: 1.2.0
+Class: nastiness
+
+if you run a parent scan, you also inherit parents for dynamic hosts.
+They routing can change on each ip address change though.
+The sanest thing is allowing to exempt them, or say that for them the folder's parent
+should not be overwriten.