[
https://issues.apache.org/jira/browse/CLOUDSTACK-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-4077:
-----------------------------------------
Priority: Critical (was: Minor)
> UI glitches for Archive/Delete events and alerts
> ------------------------------------------------
>
> Key: CLOUDSTACK-4077
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4077
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
> Affects Versions: 4.2.0
> Environment: Latest Cloudstack 4.2 build with host on KVM
> Reporter: Pavan Kumar Bandarupally
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: after-delete.jpg, before-delete.jpg, UI bug archive
> events type number.jpg, UI bug delete alerts TYPE.jpg, UI bug end date.jpg,
> UI bug start date.jpg
>
>
> In the UI page for Archive/Delete alerts and events, some of the tool-tip
> advices are misleading.
> 1) For Archive events, By event type, the tool-tip gives and advice "Archive
> all events by specifying its TYPE (integer number). For events TYPE will be
> something like USER.LOGIN and not integer value. For alerts TYPE will be
> integer number. [ UI bug archive events type number.jpg ]
> 2) 1) For Delete alerts, By event type, the tool-tip gives and advice
> "Archive all events by specifying its TYPE (USER.LOGIN). For alerts TYPE will
> be integer and not string [ UI bug delete alerts TYPE.jpg ]
> 3) For Archive events, By date, both start date and end date tool-tips bear
> same message "Archive all events which have been created after this date" .
> For end date the message should be ".... before this date" [ UI bug start
> date.jpg and UI bug end date.jpg ]
> 4) If an event is Archived individually ( by selecting archive event from the
> event Quickview description ), the event will not be removed from the UI
> until the page is reloaded. ( User has to navigate to some page or click on
> the left side events tab again for the event to disappear from UI).
> 5) When user deletes an event by type, remaining events (other than the
> deleted events) will be shown twice (redundantly) in the UI page immediately
> after the delete operation. User has to reload the page to see the events
> distinctly. [ before-delete.jpg and after-delete.jpg ]
--
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
