Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #1509] cronks page make-up (icinga web 1.4) #377

Closed
icinga-migration opened this issue May 12, 2011 · 5 comments
Closed
Labels
Milestone

Comments

@icinga-migration
Copy link

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.

@icinga-migration
Copy link
Author

Updated by tgelf on 2011-05-13 12:17:22 +00:00

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.

Cheers,
Thomas

@icinga-migration
Copy link
Author

Updated by lbetz on 2011-05-16 07:11:39 +00:00

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.

@icinga-migration
Copy link
Author

Updated by jmosshammer on 2011-05-18 06:21:52 +00:00

  • Status changed from New to Closed

fixed in master commit: fe60941

@icinga-migration
Copy link
Author

Updated by mhein on 2011-05-19 09:28:18 +00:00

  • Status changed from Closed to Assigned
  • Target Version set to 1.5

Reopen, solved on wrong commit

@icinga-migration
Copy link
Author

Updated by mhein on 2011-05-19 09:52:27 +00:00

  • Status changed from Assigned to Resolved

Okay, was fixed in fe60941, thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant