Openbravo Issue Tracking System - POS2 |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0054601 | POS2 | POS | public | 2024-02-06 21:22 | 2024-02-13 14:17 |
|
Reporter | ivazquez | |
Assigned To | SABARINATH P | |
Priority | high | Severity | major | Reproducibility | always |
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 | 0054601: When opening a store, the click is not synchronized with the correct date when you set the business date |
Description | When trying to open a store in the latest version of POS2, when you are prompted to set the Business Date, the click is not synchronized with the date, for example, if I click on day 7, it is set on day 6, or if I click on day 1, it is set on day 31 of the previous month.
Attached is a video demonstration
Reproduced in livebuilds:
https://livebuilds.openbravo.com/context/retail_pos2_modules_pgsql/web/pos/?terminal=VBS-2 [^] |
Steps To Reproduce | Try to open a till and set the Business Date |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | depends on | backport | 0054656 | 24Q1 | closed | SABARINATH P | When opening a store, the click is not synchronized with the correct date when you set the business date |
|
Attached Files | pos2BusinessDateIssue.mp4 (296,228) 2024-02-06 21:22 https://issues.openbravo.com/file_download.php?file_id=19442&type=bug |
|
Issue History |
Date Modified | Username | Field | Change |
2024-02-06 21:22 | ivazquez | New Issue | |
2024-02-06 21:22 | ivazquez | Assigned To | => Retail |
2024-02-06 21:22 | ivazquez | File Added: pos2BusinessDateIssue.mp4 | |
2024-02-06 21:22 | ivazquez | Triggers an Emergency Pack | => No |
2024-02-07 05:59 | SABARINATH P | Assigned To | Retail => SABARINATH P |
2024-02-07 14:21 | SABARINATH P | Status | new => scheduled |
2024-02-07 14:25 | SABARINATH P | Note Added: 0160344 | |
2024-02-07 14:25 | SABARINATH P | Status | scheduled => feedback |
2024-02-07 19:20 | ivazquez | Note Added: 0160363 | |
2024-02-07 19:20 | ivazquez | Status | feedback => new |
2024-02-08 18:33 | guilleaer | Note Added: 0160508 | |
2024-02-09 11:23 | egoitz | Note Added: 0160543 | |
2024-02-13 08:27 | Leyre | Type | defect => feature request |
2024-02-13 08:41 | Leyre | Type | feature request => defect |
2024-02-13 11:32 | hgbot | Note Added: 0160681 | |
2024-02-13 13:01 | guilleaer | Status | new => scheduled |
2024-02-13 14:17 | hgbot | Resolution | open => fixed |
2024-02-13 14:17 | hgbot | Status | scheduled => closed |
2024-02-13 14:17 | hgbot | Note Added: 0160693 | |
2024-02-13 14:17 | hgbot | Note Added: 0160694 | |
2024-02-13 14:17 | hgbot | Note Added: 0160695 | |
Notes |
|
|
I have tried to reproduce it in 24Q1 and PI with my time zone and also in different timezone Ex:GMT-3 in my local and browser, tried in both 24Q1 and PI instance. Still I didn't able to reproduce it. I have faced this issue long days before but it was solved later. I can't able to identify exact commit that solved this issue.
|
|
|
|
Dear Sabarinath,
Could you try to reproduce the error in the same livebuilds that I reproduced it? The video is from yesterday, so, strangely, the error is not reproduced.
Regards,
Ignacio Vazquez |
|
|
|
|
|
(0160543)
|
egoitz
|
2024-02-09 11:23
|
|
The code is already in the customer and the problem happens.
Also the recording Ignacio put is from livebuilds. |
|
|
(0160681)
|
hgbot
|
2024-02-13 11:32
|
|
|
|
(0160693)
|
hgbot
|
2024-02-13 14:17
|
|
|
|
(0160694)
|
hgbot
|
2024-02-13 14:17
|
|
|
|
(0160695)
|
hgbot
|
2024-02-13 14:17
|
|
|