Red Hat Bugzilla – Bug 593218
Alert Notification: fails to default select the alert sender type once clicked on save
Last modified: 2010-08-12 12:48:43 EDT
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):
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.
Page gets refreshed and the alert sender type is not selected by default even though the configuration for that type is not complete yet.
Once page is refreshed, the alert sender type, upon which the configuration is still pending, should be selected by default.
Author: Joseph Marques <firstname.lastname@example.org>
Date: Thu Jun 10 05:18:02 2010 -0400
BZ-599691: automatically reselect the active notification each time "SAVE"
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).
Mass-closure of verified bugs against JON.