Menu
▾
▴
[Hyperic-hq-discuss] [JIRA] Closed: (HHQ-664) Escalation Actions in Alert Details page needs to contain different
|
From: Nipuna B. (JIRA) <ji...@hy...> - 2007-03-09 00:11:37
|
[ http://jira.hyperic.com/browse/HHQ-664?page=all ] Nipuna Bhayani closed HHQ-664: ------------------------------ Escalation Action logs are displayed correctly,the actions are not bold and it was decided that it will not be bold(Confirm with Charles)-verified in release 3.0.2 build #331 > Escalation Actions in Alert Details page needs to contain different > ------------------------------------------------------------------- > > Key: HHQ-664 > URL: http://jira.hyperic.com/browse/HHQ-664 > Project: Hyperic HQ > Type: Bug > Components: Alerts > Versions: 3.0.0 > Reporter: Jon Travis > Assignee: Charles Lee > Fix For: 3.0.1 > > > Since the alert-actiion logs are no longer always tied directly to an action, we should remove the 'Action 1, 2, 3, etc.' prefix from all the actions shown on the alert details page. > Once this is done, it would be good to provide additional information about things that are done after the alert is acknowledged, fixed, etc. > Ideally, I'd like to see something like the following: > Escalation Action Logs: > 02/13/2007 01:34:46 PM - Notified users: hqadmin > 02/13/2007 01:37:01 PM - HQ Administrator acknowledged the alert (in BOLD) > 02/13/2007 01:37:05 PM - Notified users: hqadmin > 02/13/2007 01:37:03 PM - HQ Administrator fixed the alert (in BOLD) > 02/13/2007 01:37:04 PM - Notified users: hqadmin > The difference being that we can also log the things that occur as a result of acknowledging or fixing the alert. The important things (i.e. things that fixed or acknowledged an alert) should have different text treatment, so that you can see the state changing. This information is captured in the alert log as the subject. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.hyperic.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
