You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sudha Ponnaganti (JIRA)" <ji...@apache.org> on 2013/05/07 12:39:23 UTC
[jira] [Updated] (CLOUDSTACK-1904) API : UI : Admin can not delete
Events/Archive from other accounts.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudha Ponnaganti updated CLOUDSTACK-1904:
-----------------------------------------
Fix Version/s: 4.2.0
> 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
> Assignee: Sanjay Tripathi
> Fix For: 4.2.0
>
>
> 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