Bug 983275 - Defaults not honored for alert senders
Defaults not honored for alert senders
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core UI (Show other bugs)
4.8
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-10 16:20 EDT by Heiko W. Rupp
Modified: 2013-07-10 16:20 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Heiko W. Rupp 2013-07-10 16:20:41 EDT
I have the snmp alert sender that has some defaults like the var binding
prefix

Now when I just click ok to accept all defaults, that prefix is not accepted

[21:48:43] <pil-dinner>	 The failure at my demo today seems to be  UI issue where the defaults are displayed on screen but not returned back to the backend
[21:54:25] <pil-dinner>	 When I just take the displayed default in the field the resulting property is null
[21:54:54] <pil-dinner>	 If I click in the field, add a space char and then remove it again, the value is valid and the property non-null

I am now working around the issue with also providing the default in code, but this is a band-aid.

Note You need to log in before you can comment on or make changes to this bug.