[ 
https://issues.apache.org/jira/browse/AMBARI-19518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823792#comment-15823792
 ] 

Hudson commented on AMBARI-19518:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #717 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/717/])
AMBARI-19518 Log Search Troubleshooting tab should allow to multi select 
(mgergely: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f5dca1afc5b498e5aab3fb4183e5d75e6816dff5])
* (edit) 
ambari-logsearch/ambari-logsearch-portal/src/main/webapp/libs/bower/select2/select2.js
* (edit) 
ambari-logsearch/ambari-logsearch-portal/src/main/webapp/scripts/views/troubleshoot/TroubleShootLayoutView.js


> Log Search Troubleshooting tab should allow to multi select services
> --------------------------------------------------------------------
>
>                 Key: AMBARI-19518
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19518
>             Project: Ambari
>          Issue Type: Improvement
>    Affects Versions: 2.5.0
>            Reporter: Miklos Gergely
>            Assignee: Miklos Gergely
>            Priority: Minor
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19518.patch
>
>
> Customer may select multiple services on the Troubleshooting tab, and the set 
> of components should be additive. There will be two modes to select the 
> servies:
> 1. Manual mode: the customer may add/remove components manually. If the 
> customer adds/deletes any service this mode would be active, though the 
> components still there would not be removed. Also all the selected service 
> buttons will be inactivated.
> 2. Service button mode: the customer may select services with the service 
> buttons, and the components of the actually selected services would be in the 
> list. In manual mode if any service button is clicked then the service button 
> mode would be active immediately, and also the previous component list would 
> be removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to