From issues-return-90272-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org Fri Feb 23 00:46:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 0D91B18076D for ; Fri, 23 Feb 2018 00:46:03 +0100 (CET) Received: (qmail 73422 invoked by uid 500); 22 Feb 2018 23:46:03 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 73413 invoked by uid 500); 22 Feb 2018 23:46:03 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 73410 invoked by uid 99); 22 Feb 2018 23:46:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2018 23:46:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 762E9C04A0 for ; Thu, 22 Feb 2018 23:46:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id DfBRnYJqzehE for ; Thu, 22 Feb 2018 23:46:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 7A9F55F341 for ; Thu, 22 Feb 2018 23:46:01 +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 DAFF4E031B for ; Thu, 22 Feb 2018 23:46:00 +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 460EB2713A for ; Thu, 22 Feb 2018 23:46:00 +0000 (UTC) Date: Thu, 22 Feb 2018 23:46:00 +0000 (UTC) From: =?utf-8?Q?Rafael_Weing=C3=A4rtner_=28JIRA=29?= To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CLOUDSTACK-10293) Single view network ACL rules listing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-10293?page=3Dcom.at= lassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Weing=C3=A4rtner resolved CLOUDSTACK-10293. --------------------------------------------- Resolution: Fixed > Single view network ACL rules listing > ------------------------------------- > > Key: CLOUDSTACK-10293 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-102= 93 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the defa= ult.)=20 > Reporter: Rafael Weing=C3=A4rtner > Assignee: Rafael Weing=C3=A4rtner > Priority: Major > Fix For: 4.12 > > > The ACL rules editing/addition page is not user-friendly. Users are not a= ble to see in a single view all of the detail of the ACL rule (they need to= use a scroll bar on the horizontal). The problem becomes worse when there = are a considerable number of rules. Therefore, we are proposing the followi= ng changes: > # Instead of using the table to create new ACL, we can create a button li= ke the one presented in attached pictures, where users can click, and then = a modal popup would appear and users would be able to create the new ACL th= ere. This is similar to the workings of the ACL edit button. > # Remove the ability to add new ACL via table where they are presented. A= ll ACLs should be entered via the =E2=80=9CNew ACL=E2=80=9D button. Therefo= re, the section =E2=80=9CAdd ACL=E2=80=9D would be removed as well; > # Move the action section of the list ACL table to the most left position= ; > =20 > These changes would reduce the information in the table and facilitate us= ers to add new rules and easily edit them as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)