[WEBCLIENT-48] Web client gets into non-functional state Created: 09/Jan/14  Updated: 05/Jun/14  Resolved: 27/May/14

Status: Closed
Project: i2b2 Web Client
Component/s: Web Client
Affects Version/s: 1.7.00
Fix Version/s: 1.7.01

Type: Bug Priority: Critical
Reporter: George Kowalski Assignee: Mike Mendis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: happens in the 1.7.0 VM and fresh installation using Oracle and Unix

Affects View/s:
Query Tool
i2b2 Feature/s:
Timing - Panel level, Timing - Query level
Participant/s:

 Description   
OK ,

I've reproduced this on the 1.7.0 VM and my new 1.7.0 clean installation, both with the demo data provided ( both using UNIX with Oracle ) . Replicated issue with the latest versions of : Chrome, Safari and Forefox .

Follow these steps to reproduce the issue:

- Log into webclient with demo user account.
- Navigate to the term Demographics -> Gender -> Female ( don't think term matters ) in upper left "Navigate Terms" area
- Drag over the "Female" Term into the first "Group 1".
- Select the "Run Query", take the "number of patients" defaults on the pop up and see results in the Query status box below .

Ok , that all works great . but ...

- "Select the "Clear" button , ( notice that everything on the right shifts down and their is a "New Event" section near the top of the screen. )
- Select "Male" form the Term area in the upper left and drop it in the "Group 1" area.
- Select "Run Query"
- At this point the query status is not updated and no results ever return to that box.

One can mass around in and set the "Temporal Constrain" to treat all groups independently" in order to get back in a working state , but users should not need to do that to get the search to work.

George


 Comments   
Comment by Janice Donahoe [ 10/Jan/14 ]
We were able to reproduce this issue and it looks like when you click on the Clear button the Query Tool is not displaying the default settings. The Temporal Constraint is changed to "Define sequence of events" and it should default to "Treat all groups independently".

Development is working on a fix for this issue. In the meantime you can get your second query ("Male") to run if you change the Temporal constraint back to "Treat all groups independently".
Comment by George Kowalski [ 10/Jan/14 ]
Great , thanks for looking into this !
Comment by George Kowalski [ 31/Jan/14 ]
Any idea on a timeframe for getting this fixed ?
Generated at Thu Apr 18 23:22:16 UTC 2024 using Jira 8.20.11#820011-sha1:0629dd8d260e3954ece49053e565d01dabe11609.