Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ABEB11095B for ; Mon, 6 May 2013 11:42:18 +0000 (UTC) Received: (qmail 4897 invoked by uid 500); 6 May 2013 11:42:18 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 4524 invoked by uid 500); 6 May 2013 11:42:17 -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 4499 invoked by uid 500); 6 May 2013 11:42:17 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 4495 invoked by uid 99); 6 May 2013 11:42:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 May 2013 11:42:17 +0000 Date: Mon, 6 May 2013 11:42:17 +0000 (UTC) From: "Sanjay Tripathi (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-1769) Ability to delete Events and Alerts: Search by Category is required. 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-1769?page=3Dcom.atl= assian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi updated CLOUDSTACK-1769: ---------------------------------------- Fix Version/s: (was: 4.2.0) Future =20 > Ability to delete Events and Alerts: Search by Category is required. > -------------------------------------------------------------------- > > Key: CLOUDSTACK-1769 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-176= 9 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the defa= ult.)=20 > Components: API, UI > Environment: NA > Reporter: Parth Jagirdar > Assignee: Sanjay Tripathi > Fix For: Future > > > Requirement: Ability to delete alerts by a =E2=80=9Ccategory=E2=80=9D?=20 > perhaps the word =E2=80=9Ccategory=E2=80=9D was vague =E2=80=93 but, my e= xpectation that we should be able to delete by any of the following fields:= id | uuid | type| user_id | account_id | domain_id | level=20 > Delete by Type and ID is supported. I am not sure about t= he use case for user_id,account_id and domain_id . We should file a Improve= ment JIRA for it and capture the specific use cases. > ------------------- > Some Use cases:: > Admin wants to delete all events at INFO Level. > Admin wants to delete all events from account XYZ. > Admin wants to delete all events with level INFO and contains "TEXT" in d= escription=20 > (Example :: Logged in or VM stopped, started, created etc etc) > Similar functionality for Archive. > The ideas is to give ability to user to search by whats is visible on the= screen. > (And also try and leverage existing search feature than to reinvent the w= heel) > CLOUDSTACK-662 Advanced Search UI -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira