Openbravo Issue Tracking System - POS2 |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0057237 | POS2 | POS | public | 2024-11-21 15:42 | 2025-01-23 11:17 |
|
| Reporter | charlotte_vasseur | |
| Assigned To | fofarril | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | open |
| Review Assigned To | |
| OBNetwork customer | No |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0057237: [Return Input] Return Ticket / Verified Return: User input Return Line is always used when modifying the Return Input |
| Description | After choosing a return reason for products, via Return Ticket or Verified Return, when selecting 'User Input' in POS: the user input pop-up of Return Line is displayed instead of the user input linked to Return Ticket / Verified Return |
| Steps To Reproduce | In Openbravo backoffice:
Products to use for this test have 'Returnable' = Yes
In 'User Action Input’ window, define a user action input with:
- user action 'Return Line' + desired user input
- user action 'Return Ticket' + desired user input
- user action 'Verified Return Ticket' + desired user input
(see Conf User Action Input BO.png)
The POS user has a role with the required user action access configured with 'Input Request Type' = 'Defined Actions Input':
- 'Return Line'
- 'Return Ticket'
- 'Verified Return'
Login in POS with a correct user on the channel touchpoint
Add products P1 and P2
Click on the '3 dots' button and select 'Convert to return'
On the return input pop-up, the user input used is the one linked to the user action 'Return Ticket' (OK - see Return Ticket Reason when converting to return OK.png)
Select a reason and apply the same for both products
Click on a product line and select 'Return Input'
=> On the return input pop-up, the user input is not the one linked to the user
action 'Return Ticket', but the one linked to the user action 'Return Line'
(See Return Input return ticket on a product line KO.png)
Same on multi-selection of products when selecting 'Return Input'
(See Return Input return ticket on multi product lines KO.png)
Same when doing a verified return, choosing a reason and selecting 'Return Input' on a line / via multi-selection
(See Return Input verified return on multi product lines KO.png)
OK when doing a verified return, choosing a reason and selecting 'Return Input' on a line / via multi-selection
(See Return Input return line on a product line OK.png) |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files |  Conf User Action Input BO.png (80,057) 2024-11-21 15:42
https://issues.openbravo.com/file_download.php?file_id=20536&type=bug
Return Ticket Reason when converting to return OK.png (104,166) 2024-11-21 15:42
https://issues.openbravo.com/file_download.php?file_id=20537&type=bug
Return Input return ticket on a product line KO.png (117,110) 2024-11-21 15:43
https://issues.openbravo.com/file_download.php?file_id=20538&type=bug
Return Input return ticket on multi product lines KO.png (146,840) 2024-11-21 15:43
https://issues.openbravo.com/file_download.php?file_id=20539&type=bug
Return Input verified return on multi product lines KO.png (141,317) 2024-11-21 15:43
https://issues.openbravo.com/file_download.php?file_id=20540&type=bug
Return Input return line on a product line OK.png (138,721) 2024-11-21 15:43
https://issues.openbravo.com/file_download.php?file_id=20541&type=bug
|
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2024-11-21 15:42 | charlotte_vasseur | New Issue | |
| 2024-11-21 15:42 | charlotte_vasseur | Assigned To | => Retail |
| 2024-11-21 15:42 | charlotte_vasseur | File Added: Conf User Action Input BO.png | |
| 2024-11-21 15:42 | charlotte_vasseur | Triggers an Emergency Pack | => No |
| 2024-11-21 15:42 | charlotte_vasseur | File Added: Return Ticket Reason when converting to return OK.png | |
| 2024-11-21 15:43 | charlotte_vasseur | File Added: Return Input return ticket on a product line KO.png | |
| 2024-11-21 15:43 | charlotte_vasseur | File Added: Return Input return ticket on multi product lines KO.png | |
| 2024-11-21 15:43 | charlotte_vasseur | File Added: Return Input verified return on multi product lines KO.png | |
| 2024-11-21 15:43 | charlotte_vasseur | File Added: Return Input return line on a product line OK.png | |
| 2024-11-21 16:52 | charlotte_vasseur | Note Added: 0172439 | |
| 2024-12-17 20:40 | fofarril | Assigned To | Retail => fofarril |
| 2024-12-17 20:41 | fofarril | Status | new => scheduled |
| 2024-12-20 21:29 | hgbot | Merge Request Status | => open |
| 2024-12-20 21:29 | hgbot | Note Added: 0173577 | |
| 2025-01-23 11:17 | jorgewederago | Note Added: 0174576 | |
| 2025-01-23 11:17 | jorgewederago | Status | scheduled => closed |
| 2025-01-23 11:17 | jorgewederago | Resolution | open => no change required |
| 2025-01-23 11:17 | hgbot | Note Added: 0174577 | |
|
Notes |
|
|
|
This means that in case we mix verified return + return line, if we select all the lines via multi-selection and choose 'Return Input':
The 'Apply the same' checkbox should concern only the lines linked to the verified return, and another pop-up for the return line should be displayed |
|
|
|
(0173577)
|
|
hgbot
|
|
2024-12-20 21:29
|
|
|
|
|
|
|
This topic has been discussed with PrM and it is working as expected. Anything that goes outside the current approach should be handled as a new Business Requirement and follow the standard process |
|
|
|
(0174577)
|
|
hgbot
|
|
2025-01-23 11:17
|
|
|