Openbravo Issue Tracking System - Retail Modules | ||||||||||||
| View Issue Details | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
| 0045157 | Retail Modules | Web POS | public | 2020-09-29 10:37 | 2020-11-18 13:09 | |||||||
| Reporter | remibrunet | |||||||||||
| Assigned To | jorge-garcia | |||||||||||
| Priority | normal | Severity | major | Reproducibility | always | |||||||
| Status | closed | Resolution | fixed | |||||||||
| Platform | OS | 5 | OS Version | |||||||||
| Product Version | ||||||||||||
| Target Version | Fixed in Version | RR21Q1 | ||||||||||
| 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 | 0045157: [SafeBox] Same search key can't be used on different Organization | |||||||||||
| Description | Customer usually use value from 1 to 10 for their safe box, in every organization, but currently the value of a search key can't be the same among different Organization. | |||||||||||
| Steps To Reproduce | Create a safebox with search key = 1 for organization A with cash payment method Create a safebox with search key = 1 for organization B with cash payment method Connect to POS on organization A Link the safebox 1 and do a ticket in cash Remove the safebox from the menu | |||||||||||
| Proposed Solution | Put the unicity on (Organization, searchkey) level We also need to ensure that safe boxes are created at store level, otherwise more than one safe box may be visible if we only do the constraint change | |||||||||||
| Additional Information | ||||||||||||
| Tags | No tags attached. | |||||||||||
| Relationships |
| |||||||||||
| Attached Files | ||||||||||||
| Issue History | ||||||||||||
| Date Modified | Username | Field | Change | |||||||||
| 2020-09-29 10:37 | remibrunet | New Issue | ||||||||||
| 2020-09-29 10:37 | remibrunet | Assigned To | => Retail | |||||||||
| 2020-09-29 10:37 | remibrunet | Triggers an Emergency Pack | => No | |||||||||
| 2020-09-30 11:30 | javietxe | Issue Monitored: javietxe | ||||||||||
| 2020-09-30 11:30 | javietxe | Resolution time | => 1603144800 | |||||||||
| 2020-10-30 14:48 | marvintm | Resolution time | 1603144800 => 1605826800 | |||||||||
| 2020-10-30 14:48 | marvintm | Type | design defect => defect | |||||||||
| 2020-10-30 14:49 | marvintm | Proposed Solution updated | ||||||||||
| 2020-11-16 15:22 | jorge-garcia | Assigned To | Retail => jorge-garcia | |||||||||
| 2020-11-16 16:57 | hgbot | Note Added: 0124431 | ||||||||||
| 2020-11-17 08:12 | jorge-garcia | Status | new => scheduled | |||||||||
| 2020-11-18 13:09 | hgbot | Resolution | open => fixed | |||||||||
| 2020-11-18 13:09 | hgbot | Status | scheduled => closed | |||||||||
| 2020-11-18 13:09 | hgbot | Note Added: 0124479 | ||||||||||
| 2020-11-18 13:09 | hgbot | Fixed in Version | => RR21Q1 | |||||||||
| 2020-11-18 13:09 | hgbot | Note Added: 0124480 | ||||||||||
| 2020-11-18 13:09 | hgbot | Note Added: 0124481 | ||||||||||
| 2020-11-27 13:57 | javietxe | Relationship added | causes 0045525 | |||||||||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||