Openbravo Issue Tracking System - Retail Modules | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0041972 | Retail Modules | Web POS | public | 2019-10-09 16:43 | 2019-10-09 16:43 |
Reporter | plujan | ||||
Assigned To | Retail | ||||
Priority | normal | Severity | major | Reproducibility | have not tried |
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 | |||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0041972: [19Q4] [Restaurants] Message is not clear on why some tables cannot join | ||||
Description | If I pick two tables to be joint, sometimes, the combination results in an error with a non clear message "Action not allowed. The selected tables are not joined" This message is shown even for some combination that has been previously joint | ||||
Steps To Reproduce | 1. Having at least two tables with open tickets, open one. 2. Click the table field 3. Current table should be selected. Add a second table (one currently with no tickets) and Apply 4. Check the table field shows both tables now 5. Click the table field, both tables should be selected. 6. Add the other table with an open ticket from step 1 (it should be highlighted in red) 7. As expected, a message is shown. However, the message is not clear about the problem that prevents the action to be completed. 8. Remove the red table and pick a different one. This action should be valid but the message is shown again. | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2019-10-09 16:43 | plujan | New Issue | |||
2019-10-09 16:43 | plujan | Assigned To | => Retail | ||
2019-10-09 16:43 | plujan | Triggers an Emergency Pack | => No |
There are no notes attached to this issue. |