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 35E5DF42A for ; Wed, 3 Apr 2013 05:25:16 +0000 (UTC) Received: (qmail 22150 invoked by uid 500); 3 Apr 2013 05:25:16 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 22036 invoked by uid 500); 3 Apr 2013 05:25:15 -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 22018 invoked by uid 500); 3 Apr 2013 05:25:15 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 22013 invoked by uid 99); 3 Apr 2013 05:25:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Apr 2013 05:25:15 +0000 Date: Wed, 3 Apr 2013 05:25:15 +0000 (UTC) From: "Parth Jagirdar (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-1904) API : UI : Admin can not delete Events/Archive from other accounts. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Parth Jagirdar created CLOUDSTACK-1904: ------------------------------------------ Summary: API : UI : Admin can not delete Events/Archive from other accounts. Key: CLOUDSTACK-1904 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1904 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.2.0 Environment: Master # 171 Reporter: Parth Jagirdar Currently Admin can not delete events from other Users. Which voids the purpose of having Admins managing accounts. Although not mentioned explicitly in FS; An assumption is made that Admins should have full control over Alerts and Events from all Accounts. To do this, API should facilitate a way to differentiate between accounts. And perform Delete/Archive on them. As per FS: Purpose In CloudStack, we have features like Alerts and Events that helps administrator in managing the cloud. Admin can get a list of Alerts and Events but there is no way to control them i.e delete or archive them. This feature will provide the functionality to delete or archive the Alerts/Events. In this way admin can get more controls over the Alerts and Events and manage them to get required and useful information. CloudStack admin can manage them by using the APIs or through CloudStack UI. This is a functional specification of feature "Ability to delete/archive Events and Alerts" which has Jira ID CLOUDSTACK-874 However to differentiate between Accounts; additional param may be required. I.E delete all LOGIN events from account 1 but leave account 2. Similar functionality is expected for Archive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira