Bug #46038 | MEM Admin setting does not save when creating a notification group | ||
---|---|---|---|
Submitted: | 8 Jul 2009 11:12 | Modified: | 21 Jul 2009 16:09 |
Reporter: | Mark Leith | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Server | Severity: | S3 (Non-critical) |
Version: | 2.1.0.1074 | OS: | Any |
Assigned to: | Eric Herman | CPU Architecture: | Any |
[8 Jul 2009 11:12]
Mark Leith
[8 Jul 2009 16:13]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Verified the issue is in build 2.1.0.1074.
[9 Jul 2009 0:27]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch applied in versions => 2.1.0.1075.
[9 Jul 2009 18:26]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Verified fixed in service manager build 2.1.0.1075.
[21 Jul 2009 16:09]
Tony Bedford
An entry was added to the 2.1.0 changelog: In the Enterprise Dashboard, if a Notification Group was created, and also set to be the “MEM Admin” for cry for help emails, the MEM Admin column showed as "false" in the table overview when the group was saved. However, if the group was then edited and the flag added again, the MEM Admin status was saved.