Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0016002
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] B. User interfacemajorsometimes2011-02-17 23:012011-10-29 22:07
ReporterjohnfandlView Statuspublic 
Assigned Tomtaal 
PriorityurgentResolutionunable to reproduceFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version3.0MP6
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0016002: Subtle timing problem with column filters

DescriptionIf you type the characters at just the right speed, you can get incorrect filter results. This effect does not happen consistently. I stumbled on it, but can make it happed about 1 in 4 times.
Steps To Reproduce1. Select Tables and Columns
2. Reset any filters you may have
3. On the Name column, type the string part (for partner)
4. There should be 15 rows showing, but sometimes there are 27 (which is the result set for a query on par.

So, the query is sent at 'par', but the system sometimes does not detect that the t has been typed (so it does not send a new query). The result is that the user is shown too many rows (those containing the string par, instead of those containing the string part).
Proposed SolutionProgram must continue to detect new keystrokes, after query has been sent.
TagsNo tags attached.
Attached Filespng file icon shows_27_rows_should_show_15.PNG [^] (130,872 bytes) 2011-02-17 23:01


png file icon correctly_shows_15_rows_when_filtering_on_part.PNG [^] (108,661 bytes) 2011-02-17 23:04

- Relationships Relation Graph ] Dependency Graph ]
depends on defect 0018137 closedmtaal Incorrect filtering on slow tables 

-  Notes
(0034257)
johnfandl (reporter)
2011-02-17 23:09

I put this at severity "Major" because:

1. I assume this is a general platform defect, not just for this sample menu option
2. It can result in misleading data and wrong decisions

Re: 2, consider a querylist widget with subtotals, which will be overstated in this case. If a busy user does not notice the subtle problem, she could make a wrong decision based on bad data.

Note that the problem is easier to reproduce against larger datasets. I expect that users will be noticing this, and it will undermine confidence in the system.

- Issue History
Date Modified Username Field Change
2011-02-17 23:01 johnfandl New Issue
2011-02-17 23:01 johnfandl Assigned To => dbaz
2011-02-17 23:01 johnfandl File Added: shows_27_rows_should_show_15.PNG
2011-02-17 23:01 johnfandl Modules => Core
2011-02-17 23:03 dbaz Assigned To dbaz => mtaal
2011-02-17 23:04 johnfandl File Added: correctly_shows_15_rows_when_filtering_on_part.PNG
2011-02-17 23:09 johnfandl Note Added: 0034257
2011-02-21 08:24 alostale Status new => scheduled
2011-08-01 12:24 psarobe Priority normal => urgent
2011-08-01 12:24 psarobe Target Version => 3.0MP3
2011-08-01 12:25 psarobe Relationship added depends on 0018137
2011-08-31 09:44 mtaal Target Version 3.0MP3 => 3.0MP4
2011-09-18 12:52 mtaal Target Version 3.0MP4 => 3.0MP5
2011-10-25 08:00 mtaal Target Version 3.0MP5 => 3.0MP6
2011-10-29 22:07 psarobe Status scheduled => closed
2011-10-29 22:07 psarobe Resolution open => unable to reproduce


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker