Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BD8A8200C54 for ; Wed, 29 Mar 2017 00:08:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BC075160B9B; Tue, 28 Mar 2017 22:08:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 10B35160B89 for ; Wed, 29 Mar 2017 00:08:44 +0200 (CEST) Received: (qmail 30792 invoked by uid 500); 28 Mar 2017 22:08:44 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 30783 invoked by uid 99); 28 Mar 2017 22:08:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Mar 2017 22:08:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id C7E641A07B9 for ; Tue, 28 Mar 2017 22:08:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 4EiN_Z2MEWGm for ; Tue, 28 Mar 2017 22:08:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 909C05FB20 for ; Tue, 28 Mar 2017 22:08:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id CB44FE002F for ; Tue, 28 Mar 2017 22:08:41 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 8394E24062 for ; Tue, 28 Mar 2017 22:08:41 +0000 (UTC) Date: Tue, 28 Mar 2017 22:08:41 +0000 (UTC) From: "Richard Zang (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-20613) Host Filtering interaction is confusing and cumbersome to perform simple filtering MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Mar 2017 22:08:45 -0000 Richard Zang created AMBARI-20613: ------------------------------------- Summary: Host Filtering interaction is confusing and cumbersome to perform simple filtering Key: AMBARI-20613 URL: https://issues.apache.org/jira/browse/AMBARI-20613 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.1 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.1 The new Host filtering was implemented for 2.4.0. This allowed for more sophisticated filtering, but made certain tasks more difficult, like a simple substring match on hostnames, which is part of a typical workflow and doing bulk ops on hosts. The major challenge from the user standpoint is that the new host filter aggressively pushes typeahead selections to the user, so it is really difficult to enter a simple search term that the user wants to enter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)