Bug 593218

Summary: Alert Notification: fails to default select the alert sender type once clicked on save
Product: [Other] RHQ Project Reporter: Sudhir D <sdharane>
Component: AlertsAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Corey Welton <cwelton>
Severity: medium Docs Contact:
Priority: high    
Version: 3.0.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 2.4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 599691 (view as bug list) Environment:
Last Closed: 2010-08-12 16:48:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 577217, 599691    

Description Sudhir D 2010-05-18 08:26:17 UTC 
Description of problem:
While creating a new alert sender type, the page fails to default select the alert sender type that is being configured upon.

Version-Release number of selected component (if applicable):
Build# 152.

How reproducible:
Always

Steps to Reproduce:
1.Create a new alert definition.
2.Click on Edit for the Alert Notification.
3.On the Alert notification page, click on Add New. Select the Alert sender type as Resource Operations.
4.Select the resource selection mode as Relative Resource. 
5.Click Save
  
Actual results:
Page gets refreshed and the alert sender type is not selected by default even though the configuration for that type is not complete yet.

Expected results:
Once page is refreshed, the alert sender type, upon which the configuration is still pending, should be selected by default.

Additional info:
Comment 1 Corey Welton 2010-06-10 18:04:48 UTC 
commit 2674a1413dd7f6edaf2f4757d508125fdbabd6f5
Author: Joseph Marques <joseph>
Date:   Thu Jun 10 05:18:02 2010 -0400

    BZ-599691: automatically reselect the active notification each time "SAVE"
is pressed

    figure out which one should be selected from the backing store.  updating
    an alert notification will overwrite all existing notifications with the
    latest data.  since the ids of the alert notifications are different after
    a save-action, but since we know what the updated data, we can select the
    correct one by testing for data equality (instead of pk/id equality).
Comment 2 Corey Welton 2010-06-10 18:14:09 UTC 
QA Verified.
Comment 3 Corey Welton 2010-08-12 16:48:43 UTC 
Mass-closure of verified bugs against JON.