Created attachment 394647 [details] Stack trace Description of problem: If a user navigates to a Resource page, traverses to the Alert History page (via Alert->History), then clicks on the Alert Definition link for any alert that has fired, they will be presented with a stack trace similar to the one attached. Version-Release number of selected component (if applicable): RHQ, 2/16 git pull, alertPlugin branch How reproducible: Always Steps to Reproduce: 1. Create an alert definition for a resource and wait for it to fire 2. Goto (resource page)->Alert->History 3. Click the link corresponding to the definition you just created Actual results: Stack trace similar to that attached Expected results: Corresponding Alert Definition page renders Additional info:
mass move to rhq_chainsaw tracker bug
This bug has now been triaged by Chainsaw on 2/18. The expectation is the bug to be addressed by the end of sprint06 roughly 3/10/10.
Fixed in b5e46e4 (branch alertPlugin)
Verified on commit 3602414a6baff7fb52d637d2006574610212b46f verified that clicking the alert definition from the local and global history works
moving verified bugs to rhq_sprint06, and removing from rhq_chainsaw
Mass-closure of verified bugs against JON.