Bug 983275 - Defaults not honored for alert senders
Summary: Defaults not honored for alert senders
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-10 20:20 UTC by Heiko W. Rupp
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Heiko W. Rupp 2013-07-10 20:20:41 UTC
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.