Bug 1402392 - When creating advanced search with "Count of" integer value not blank error when integer is filled in
Summary: When creating advanced search with "Count of" integer value not blank error w...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Jozef Zigmund
QA Contact: Angelina Vasileva
URL:
Whiteboard: ui:search:filter
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 12:41 UTC by Matouš Mojžíš
Modified: 2019-05-31 15:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-20 17:44:26 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)
integer empty error (69.12 KB, image/png)
2016-12-07 12:41 UTC, Matouš Mojžíš
no flags Details

Description Matouš Mojžíš 2016-12-07 12:41:20 UTC
Created attachment 1229050 [details]
integer empty error

Description of problem:


Version-Release number of selected component (if applicable):
5.7.0.14

How reproducible:
Always

Steps to Reproduce:
1. Create advanced search expression eleemtn with type "Count of"
2. Fill in number
3.

Actual results:
Field Value Error: Integer value must not be blank

Expected results:


Additional info:
Maybe the same thing as with this BZ when typing faster than appliance can process:
https://bugzilla.redhat.com/show_bug.cgi?id=1349499

Comment 2 Jozef Zigmund 2017-02-20 13:11:49 UTC
Hi Matous, yea I think it's the same thing with the fast typing (the request when user types, it's not fully solved at the moment of applying advanced search). Because I'm not able to reproduce that on my local machine - the request are solved immediately.

Comment 3 Matouš Mojžíš 2017-03-03 15:06:56 UTC
Verified in 5.7.1.3. No error occurred after creating advanced search with "count of".


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