Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0052143 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [POS2] POS | major | always | 2023-04-17 18:50 | 2023-04-18 11:35 | |||
| Reporter | gorka_gil | View Status | public | |||||
| Assigned To | Retail | |||||||
| Priority | low | Resolution | no change required | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Review Assigned To | ||||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0052143: Pager flow: next button saves | |||||||
| Description | Pager code it is applied clicking back/next | |||||||
| Steps To Reproduce | - Go to the POS2 terminal and log in - Type 'Carbonio Helmet' in the POS2 search bar and add it - When the first step of the pager view appears, click 'Next' to go to the second step - Press any number of the keypad, for example 1 - Click apply -> it will close the setup and the info is correct in the ticket - select the line of the ticket, - select in the menu "edit pager information", it will open the pager setup - go to next step - change the 1 to 2 - go back - press next ERROR: the pager in the ticket line has change from 1 to 2, it should not apply the change in the next, but only the apply | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||||
|
|||||||||||||||
 Relationships |
|
Notes |
|
|
(0148522) mtaal (manager) 2023-04-18 09:26 |
I think error 1 is by-design (not an error, maybe a design defect). The pager setting works the same as product configuration. When you change a product modifier in a flow it also updates the ticket line right away. |
|
(0148528) gorka_gil (administrator) 2023-04-18 11:35 |
Closing the issue, since this behavior it is the intended one. Created another issue to track the lost of the code in the input going back and forward: https://issues.openbravo.com/view.php?id=52146 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2023-04-17 18:50 | gorka_gil | New Issue | |
| 2023-04-17 18:50 | gorka_gil | Assigned To | => Retail |
| 2023-04-17 18:50 | gorka_gil | Triggers an Emergency Pack | => No |
| 2023-04-17 18:50 | gorka_gil | Relationship added | related to 0051891 |
| 2023-04-18 09:26 | mtaal | Note Added: 0148522 | |
| 2023-04-18 11:33 | gorka_gil | Description Updated | View Revisions |
| 2023-04-18 11:33 | gorka_gil | Steps to Reproduce Updated | View Revisions |
| 2023-04-18 11:35 | gorka_gil | Note Added: 0148528 | |
| 2023-04-18 11:35 | gorka_gil | Status | new => closed |
| 2023-04-18 11:35 | gorka_gil | Resolution | open => no change required |
| 2023-04-18 11:35 | gorka_gil | Relationship added | related to 0052146 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |