[dev.icinga.com #2161] remove content of errors section in icinga-web and link to wiki #271

icinga-migration opened this Issue Dec 7, 2011 · 8 comments


None yet

1 participant


This issue has been migrated from Redmine: https://dev.icinga.com/issues/2161

Created by mfriedrich on 2011-12-07 08:56:09 +00:00

Assignee: Wolfgang
Status: Closed (closed on 2015-05-01 12:48:37 +00:00)
Target Version: (none)
Last Update: 2015-05-01 12:48:37 +00:00 (in Redmine)

Icinga Version: 1.7.1

we are keeping a lot of duplicated information over there, and for better reading, i'd suggest merging that somehow to the wiki (maybe create a sub page to the icinga web testing page) and then finally link over there from the docs. people should get more aware of how to test the web if an error occurs.



Updated by Wolfgang on 2011-12-07 18:00:03 +00:00

  • Status changed from New to Feedback

What about the people without internet access?


Updated by mfriedrich on 2011-12-07 18:01:58 +00:00

if so, then you have to make sure that the errors section remains uptodate. this is currently not really the case.


Updated by Wolfgang on 2012-04-28 16:39:12 +00:00

  • Status changed from Feedback to Assigned
  • Assigned to set to Wolfgang
  • Done % changed from 0 to 20

added a hint on fool's day in r1.7 (missed to mention that)


Updated by mfriedrich on 2012-04-30 16:26:55 +00:00

can you please make that an url? my docbook2html generates text only.


Updated by Wolfgang on 2012-04-30 21:33:43 +00:00

  • Done % changed from 20 to 30

changed to clickable link


Updated by mfriedrich on 2012-05-03 10:40:21 +00:00

  • Target Version changed from 1.7 to 1.8

ok that's fine for 1.7, rest should be discussed for 1.8


Updated by mfriedrich on 2012-09-03 17:51:23 +00:00

  • Target Version deleted 1.8
  • Icinga Version set to 1
  • (unknown custom field) set to Debian

postpone the dicussion to real life on the conference.


Updated by mfriedrich on 2015-05-01 12:48:37 +00:00

  • Status changed from Assigned to Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment