Description of problem: JON alert email report says "This message was delivered to you by RHQ." Version-Release number of selected component (if applicable): JBoss Operations Network Version : 3.2.0.ER7 Build Number : e8e6401:ff0061d GWT Version : 2.5.0 SmartGWT Version : 3.0p How reproducible: always Steps to Reproduce: 1. Create an alert definition and configure with email notification 2. On the alert notification says on the bottom "This message was delivered to you by RHQ." Actual results: says "This message was delivered to you by RHQ." Expected results: Should be "This message was delivered to you by JBOSS Operations Network." Additional info: --------------Email snap------------------- Subject: [ALERT] priority of [Medium] for alert [107-email-test] on resource [RHQ Agent] The resource RHQ Agent has generated the following alert: ------------------------------------------ Resource Name : RHQ Agent Alert Name : 107-email-test Alert Severity : Medium Alert Date/Time : Fri Nov 29 17:31:16 IST 2013 Conditions: - Condition 1: JVM Free Memory > 1,024.0B - Date/Time: 2013/11/29 17:31:11 IST - Details: 40.1MB ------------------------------------------ Resource Ancestry: rhel6-vm [Platforms, Linux] RHQ Agent [RHQAgent, RHQ Agent] ------------------------------------------ For additional details about this alert, go to http://rhel-vm-2:7080/coregui/CoreGUI.html#Resource/10723/Alerts/History/10042 This message was delivered to you by RHQ. --------------Email snap-------------------
This is not a regression, it's a bit of branding we don't currently do. Moving it out of 3.3.0.GA and asking for PM triage.
branch: master link: https://github.com/rhq-project/rhq/commit/cf4394524 time: 2014-11-10 13:37:44 +0100 commit: cf4394524b71e0f7ab6c4ec9b8304e0dd4cc77c0 author: Libor Zoubek - lzoubek message: Bug 1036101 - BRANDING: JON alert email report says "This message was delivered to you by RHQ." EmailManagerBean now looks up productName and puts it into alert-email body
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121. This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.