Openbravo Issue Tracking System - Retail Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0035143 | Retail Modules | Web POS | public | 2017-02-02 16:45 | 2017-02-02 16:45 |
| Reporter | lorenzofidalgo | ||||
| Assigned To | Retail | ||||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | main | ||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | No | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0035143: [RR17Q1] Pay Open Tickets search query takes too long | ||||
| Description | Pay Open Tickets search query takes too long in some contexts. I have been able to reproduce this issue in a RR17Q1 Store Server with HighVol context. Currently it is taking longer than 4 minutes using Start Date and End Date filters. | ||||
| Steps To Reproduce | 0-Login POS as vallblanca. 1-Click dropdown menu and select Pay Open Tickets. 2A-In the just opened popup, click Search button. DEFECT: It will take too long. 2B-You can also check to use Date filters before clicking Search button. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | https://issues.openbravo.com/file_download.php?file_id=10385&type=bug | ||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2017-02-02 16:45 | lorenzofidalgo | New Issue | |||
| 2017-02-02 16:45 | lorenzofidalgo | Assigned To | => Retail | ||
| 2017-02-02 16:45 | lorenzofidalgo | File Added: PayOpenTickets.png | |||
| 2017-02-02 16:45 | lorenzofidalgo | OBNetwork customer | => No | ||
| 2017-02-02 16:45 | lorenzofidalgo | Triggers an Emergency Pack | => No | ||
| There are no notes attached to this issue. |