Bug 1394287 - [RFE] Notification severity levels should match the levels of $evm.log
Summary: [RFE] Notification severity levels should match the levels of $evm.log
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: John Hardy
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-11 15:02 UTC by Peter McGowan
Modified: 2019-07-08 12:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-08 12:06:17 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Peter McGowan 2016-11-11 15:02:57 UTC 
Description of problem:
It would be more intuitive to use if the severity levels for $evm.create_notification (currently 'success', 'info', 'warning' and 'error') were the same as the severity levels for $evm.log (currently 'unknown', 'fatal', 'error', 'warn', 'info' and 'debug'). 

This RFE is to suggest keeping 'success', change 'warning' to 'warn', and add 'fatal' and possibly 'unknown' to the severity levels for $evm.create_notification.

Version-Release number of selected component (if applicable):
5.7.0.10-beta3.20161109111947_9a61b18
Comment 2 Greg McCullough 2016-11-11 15:27:57 UTC 
Gregg - Can you review this request as I think these changes need to be made on the backend first before automate can utilize them.  Let me know if you want to discuss.
Note You need to log in before you can comment on or make changes to this bug.