[WEBCLIENT-50] New Events for temporal queries are mislabled after using 'Clear' Created: 06/Feb/14 Updated: 29/Oct/14 Resolved: 29/Oct/14 |
|
Status: | Closed |
Project: | i2b2 Web Client |
Component/s: | Web Client |
Affects Version/s: | 1.7.00 |
Fix Version/s: | 1.7.04 |
Type: | Bug | Priority: | Trivial |
Reporter: | Michael Horvath | Assignee: | Janice Donahoe |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: | win7, chrome |
Attachments: |
![]() ![]() |
Affects View/s: |
Query Tool
|
i2b2 Feature/s: |
Temporal Queries
|
i2b2 Sponsored Project/s: |
i2b2 Core
|
Affects Web Browser/s: |
All Web Browsers
|
Reproduction Notes: | Environment: i2b2 1.7 Test Environment
1. In the query tool, add a third event. 2. Click on the Clear button. 3. The Query Tool clears the query and returns to the default settings 4. Select Define Sequence of Events. 5. Add an Event. 6. Notice the Event Name that appears still says Event 2 (the field is not updated). 7. Look at the drop down menu and notice "Event 3" appears in the list twice. 8. Now go to the Define Order of Events page. 9. Click on the drop down that says Event 1. 10. Notice "Event 3" appears twice. |
Developer Notes: | Fixed by Mike Mendis |
Testing Notes: | Still not working. Tested with the latest build and Event 3 continues to appear in the drop down list twice.
Attached screen prints are from testing in Firefox on a windows machine. ----------------------------------------------------- Tested with the latest build and it is now working correctly. |
Participant/s: | |
Build Number (Fixed): | 1.7.04.0004 |
Description |
If you add new events using the 'Define Sequence of Events' function, it will always start labeling the events at 3 after you 'Clear' the query. Reproduce: Click New Event Click Clear Click New Event results in "Event 1" "Event 2" "Define Order of Events" "Event 3" "Event 3" |
Comments |
Comment by Janice Donahoe [ 14/May/14 ] |
This issue can be reproduced in the 1.7.01 version of i2b2. It will be evaluated by the i2b2 team for a fix to be included into version 1.7.02. |
Comment by Janice Donahoe [ 12/Aug/14 ] |
This is still an issue. It was inadvertently changed to resolved. Will be addressed in 1.7.04. |