incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pranav Saxena (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-486) Clicking UI notifications for System VM or Virtual Router opens Instances page
Date Thu, 27 Dec 2012 07:58:12 GMT


Pranav Saxena commented on CLOUDSTACK-486:

I think is mainly for the fact that the traversal has to start from "instances" section since
before that we have the "dashboard" section which is the cloudstack UI's first page itself.
Hence in order to iterate over the list of sections , "instances" has been passed to the notification
widget. Let me deep dive into this issue and think of a solution to handle this . 

Thanks ,
> Clicking UI notifications for System VM or Virtual Router opens Instances page
> ------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-486
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.0.0
>            Reporter: Kirk Kosinski
>            Assignee: Pranav Saxena
>            Priority: Minor
> If you click a notification in the UI for a System VM or Virtual Router, instead of opening
the relevant System VMs or Virtual Routers page, the Instances page is opened. This is not
useful since System VMs and Virtual Routers do not show up on the Instances page. The relevant
page should be opened instead.
> To reproduce:
> 1. Log on to the UI.
> 2. Navigate to Infrastructure > System VMs or Virtual Routers.
> 3. Perform an action on one of them. For example, stop a System VM.
> 4. Wait for a notification to be generated. 
> 5. Open the notifications list and click on the notification. For the example in step
3, click "Stop System VM".
> 6. Notice that the Instances page is opened.

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:

View raw message