ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AMBARI-16432) Give user visual feedback while we do background request and next button is disabled
Date Wed, 11 May 2016 11:49:13 GMT


Hudson commented on AMBARI-16432:

FAILURE: Integrated in Ambari-trunk-Commit #4821 (See [])
AMBARI-16432. Give user visual feedback while we do background request (onechiporenko: [])
* ambari-web/app/routes/high_availability_routes.js
* ambari-web/test/controllers/main/service/reassign/step4_controller_test.js
* ambari-web/app/templates/common/assign_master_components.hbs
* ambari-web/test/controllers/main/admin/kerberos/kerberos_wizard_controler_test.js
* ambari-web/app/templates/wizard/step7.hbs
* ambari-web/test/controllers/main/admin/kerberos/step1_controller_test.js
* ambari-web/app/routes/add_service_routes.js
* ambari-web/test/controllers/main/admin/kerberos/step2_controller_test.js
* ambari-web/app/views/common/global/spinner.js
* ambari-web/app/controllers/wizard/step6_controller.js
* ambari-web/app/templates/main/admin/highAvailability/nameNode/step3.hbs
* ambari-web/app/templates/wizard/step6.hbs
* ambari-web/app/routes/add_host_routes.js
* ambari-web/app/controllers/wizard/step4_controller.js
* ambari-web/app/controllers/wizard/step7_controller.js
* ambari-web/test/views/main/service/services/hive_test.js
* ambari-web/test/controllers/installer_test.js
* ambari-web/app/routes/installer.js

> Give user visual feedback while we do background request and next button is disabled
> ------------------------------------------------------------------------------------
>                 Key: AMBARI-16432
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>            Priority: Critical
>             Fix For: 2.4.0
>         Attachments: AMBARI-16432.patch
> User may think that he is blocked or did something wrong, on one of wizard (any wiz)
steps because Next button can be disabled (on significant time), especially on big clusters
or in case of slow connection speed, or bad ping. 
> We have many places where we disable "Next" button while we do some background operations/calculations.
Usually this are requests on validations/recommendations. Sometimes this can take a significant
time frame, before we will enable Next button. At the same time user is not aware why Next
button is disabled and he cannot proceed to next step. We should give user a visual feedback
that we are doing some calculations and that's why Next button is disabled. The easiest way
is, to switch Next button on spinner while we do our background stuff.

This message was sent by Atlassian JIRA

View raw message