New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #8247] Move notifications to the bottom of the page #1318
Comments
Updated by tgelf on 2015-02-02 22:03:14 +00:00 We will probably move notifications to the bottom of the page, this will be addressed after beta2. Cheers, |
Updated by elippmann on 2015-03-31 13:51:13 +00:00
|
Updated by aklimov on 2015-05-29 10:25:51 +00:00
|
Updated by aklimov on 2015-05-29 12:19:45 +00:00
|
Updated by jcasale on 2015-06-06 00:56:37 +00:00 Hi aklimov, |
Updated by jmeyer on 2015-06-11 08:27:02 +00:00
|
Updated by jmeyer on 2015-06-17 10:02:20 +00:00 jcasale wrote:
Hi jcasale, this does not seem to be related with this issue, please create another issue if the mentioned problem still exists, thanks. Best regards, |
Updated by jmeyer on 2015-06-17 10:55:20 +00:00
|
Updated by jmeyer on 2015-06-17 10:59:35 +00:00
Applied in changeset 460ea75. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8247
Created by jcasale on 2015-01-17 21:50:51 +00:00
Assignee: jmeyer
Status: Resolved (closed on 2015-06-17 10:59:35 +00:00)
Target Version: 2.0.0-rc1
Last Update: 2015-06-17 10:59:35 +00:00 (in Redmine)
I think it is certainly imperative to know if the check has been scheduled and the success or failure of that request however shifting the users page down is disruptive. I can work far faster than the browser's recovery time and this is disruptive. If the check is scheduled asynchronously, could a static indication provide status or something along that lines such that I can continue to work and if something has gone wrong that I need to look into, I can be alerted non disruptively?
Thanks.
Changesets
2015-05-29 12:17:12 +00:00 by aklimov 0ba4d24
2015-06-17 10:54:36 +00:00 by jmeyer 31406a7
2015-06-17 10:56:51 +00:00 by jmeyer 460ea75
The text was updated successfully, but these errors were encountered: