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-05-19 09:52:27 +00:00)
Target Version: 1.5
Last Update: 2011-05-19 09:52:27 +00:00 (in Redmine)
Selecting a cronk like service status you get a list of page.maxItems items, first. Shortly after you get the whole list of all service items in this cronk.
This behavior doesn't appears, after selecting the 2nd page.
The text was updated successfully, but these errors were encountered:
Could you kindly add a step-by-step description showing how to reproduce this? I first thought I was able to do so - but after changing some prefs (fewer rows, earlier refreshes) it never happened again.
Once proved to be a real issue, priority shall IMO be raised and the ticket subject changed to something more meaningful.
After logged in, in my Case I have over 600 critical services, I choose this cronk. First, always seems to correct and I get the first 25 criticals. But then I can't do anything on the site, till the site loaded and announced all criticals in the cronk.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/1509
Created by lbetz on 2011-05-12 12:48:15 +00:00
Assignee: mhein
Status: Resolved (closed on 2011-05-19 09:52:27 +00:00)
Target Version: 1.5
Last Update: 2011-05-19 09:52:27 +00:00 (in Redmine)
Selecting a cronk like service status you get a list of page.maxItems items, first. Shortly after you get the whole list of all service items in this cronk.
This behavior doesn't appears, after selecting the 2nd page.
The text was updated successfully, but these errors were encountered: