Bug 1025590 - [RFE][TESTING][Search Runs] 'Reset' button cannot clear the condition fields after a search
[RFE][TESTING][Search Runs] 'Reset' button cannot clear the condition fields ...
Status: CLOSED NOTABUG
Product: TCMS
Classification: Other
Component: Application (Show other bugs)
3.8.5
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Yuguang Wang
tools-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-31 23:00 EDT by Chen Chen
Modified: 2014-08-05 21:22 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-08-05 21:22:00 EDT
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 Chen Chen 2013-10-31 23:00:35 EDT
Description of problem:
Go to 'TESTING'->'Search Runs' page, input some search conditions, click 'Search' button, after the results are shown, click 'Reset' button, at this time 'Reset' button cannot clear the condition fields.

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

How reproducible:
100%

Steps to Reproduce:
1.Go to 'TESTING'->'Search Runs' page, input some search conditions, click 'Search' button.
2.after the results are shown, click 'Reset' button

Actual results:
2.'Reset' button cannot clear the condition fields.

Expected results:
2.'Reset' button can clear the condition fields.

Additional info:
Before do a search, 'Reset' can clear the condition fields.
Comment 2 cqi 2014-08-05 21:22:00 EDT
Reset button is a simple and primordial HTML form input element without any other modification with JavaScript. Thus, reset button resets each INPUT's value back to the original in the INPUT value attribute, not clear text box.

Search Runs feature is capable of remembering previous search criteria entered and selected by user. This is why the fact this bug is describing happens.

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