Openbravo Issue Tracking System - POS2 |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0051445 | POS2 | POS | public | 2023-01-23 18:04 | 2023-03-20 11:54 |
|
Reporter | javierRodriguez | |
Assigned To | javierRodriguez | |
Priority | normal | Severity | major | Reproducibility | have not tried |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
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 | 0051445: Create a mechanism to detect that POS is working with a duplicated ticket id |
Description | After severals cases in production where the application is working with a brand new ticket which has a used id. This creates EWIs due to try to synchronise a ticket with duplicates ids. |
Steps To Reproduce | In production, this problem appeared after an F5 (refresh) or after a delete ticket action. |
Proposed Solution | This duplicated id should be checked:
- After an F5
- When a new ticket is set in Ticket state model
The application could have different scenarios when a ticket is set in the state. Ticket could be
- Processed tickets
- brand new tickets
- No-processed ticket which are in ticket list with products or payments on it.
It is necessary to take into account this different scenarios and do actions depending on them. |
Additional Information | |
Tags | No tags attached. |
Relationships | depends on | backport | 0051535 | 23Q1 | closed | javierRodriguez | Create a mechanism to detect that POS is working with a duplicated ticket id | depends on | backport | 0051811 | 22Q4.3 | closed | javierRodriguez | Create a mechanism to detect that POS is working with a duplicated ticket id |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2023-01-23 18:04 | javierRodriguez | New Issue | |
2023-01-23 18:04 | javierRodriguez | Assigned To | => javierRodriguez |
2023-01-23 18:04 | javierRodriguez | Triggers an Emergency Pack | => No |
2023-01-31 16:54 | hgbot | Note Added: 0146100 | |
2023-01-31 17:52 | hgbot | Note Added: 0146105 | |
2023-02-02 12:36 | guilleaer | Status | new => scheduled |
2023-02-02 12:36 | guilleaer | Status | scheduled => acknowledged |
2023-02-02 12:37 | guilleaer | Status | acknowledged => scheduled |
2023-02-03 11:04 | hgbot | Resolution | open => fixed |
2023-02-03 11:04 | hgbot | Status | scheduled => closed |
2023-02-03 11:04 | hgbot | Note Added: 0146250 | |
2023-02-03 11:04 | hgbot | Fixed in Version | => RR23Q2 |
2023-02-03 11:04 | hgbot | Note Added: 0146251 | |
2023-02-03 11:04 | hgbot | Note Added: 0146252 | |
2023-02-03 11:04 | hgbot | Note Added: 0146253 | |
2023-02-09 18:51 | javierRodriguez | Status | closed => new |
2023-02-09 18:51 | javierRodriguez | Resolution | fixed => open |
2023-02-09 18:51 | javierRodriguez | Fixed in Version | RR23Q2 => |
2023-02-10 11:31 | hgbot | Note Added: 0146367 | |
2023-02-10 13:29 | hgbot | Note Added: 0146384 | |
2023-02-10 13:29 | hgbot | Note Added: 0146385 | |
2023-02-10 13:34 | javierRodriguez | Status | new => scheduled |
2023-02-10 13:34 | javierRodriguez | Status | scheduled => resolved |
2023-02-10 13:34 | javierRodriguez | Resolution | open => fixed |
2023-02-10 13:34 | javierRodriguez | Status | resolved => closed |
2023-02-16 21:43 | hgbot | Note Added: 0146665 | |
2023-02-16 21:45 | hgbot | Note Added: 0146666 | |
2023-02-20 08:34 | hgbot | Note Added: 0146742 | |
2023-02-20 08:34 | hgbot | Note Added: 0146743 | |
2023-02-20 08:34 | hgbot | Note Added: 0146744 | |
2023-02-20 08:34 | hgbot | Note Added: 0146745 | |
2023-02-20 08:34 | hgbot | Note Added: 0146746 | |
2023-02-20 08:34 | hgbot | Note Added: 0146747 | |
2023-03-08 13:34 | javierRodriguez | Status | closed => new |
2023-03-08 13:34 | javierRodriguez | Resolution | fixed => open |
2023-03-08 13:34 | javierRodriguez | Status | new => scheduled |
2023-03-08 13:37 | javierRodriguez | Status | scheduled => resolved |
2023-03-08 13:37 | javierRodriguez | Resolution | open => fixed |
2023-03-20 11:54 | javierRodriguez | Status | resolved => closed |
Notes |
|
(0146100)
|
hgbot
|
2023-01-31 16:54
|
|
|
|
(0146105)
|
hgbot
|
2023-01-31 17:52
|
|
|
|
(0146250)
|
hgbot
|
2023-02-03 11:04
|
|
|
|
(0146251)
|
hgbot
|
2023-02-03 11:04
|
|
|
|
(0146252)
|
hgbot
|
2023-02-03 11:04
|
|
|
|
(0146253)
|
hgbot
|
2023-02-03 11:04
|
|
|
|
(0146367)
|
hgbot
|
2023-02-10 11:31
|
|
|
|
(0146384)
|
hgbot
|
2023-02-10 13:29
|
|
|
|
(0146385)
|
hgbot
|
2023-02-10 13:29
|
|
|
|
(0146665)
|
hgbot
|
2023-02-16 21:43
|
|
|
|
(0146666)
|
hgbot
|
2023-02-16 21:45
|
|
|
|
(0146742)
|
hgbot
|
2023-02-20 08:34
|
|
|
|
(0146743)
|
hgbot
|
2023-02-20 08:34
|
|
|
|
(0146744)
|
hgbot
|
2023-02-20 08:34
|
|
|
|
(0146745)
|
hgbot
|
2023-02-20 08:34
|
|
|
|
(0146746)
|
hgbot
|
2023-02-20 08:34
|
|
|
|
(0146747)
|
hgbot
|
2023-02-20 08:34
|
|
|