Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0057206 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [POS2] POS | minor | always | 2024-11-20 11:59 | 2024-11-20 12:05 | |||||||
| Reporter | fdomingues | View Status | public | |||||||||
| Assigned To | Retail | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | PostgreSQL | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | 24Q3.2 | SCM revision | ||||||||||
| Review Assigned To | ||||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0057206: Return Ticket Reason displayed when a return is converted into an order | |||||||||||
| Description | Reasons always displayed under the products lines after convert a return into an order | |||||||||||
| Steps To Reproduce | Prerequisites: • 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 Ticket' • desired user input • The POS user has a role with the required user action access 'Return Ticket' configured with 'Input Request Type' = 'Defined Actions Input' • Login in POS with a correct user on the channel touchpoint Steps: Add products P1 and P2 to the ticket Click on the '3 dots' button and select 'Convert to return' On the 'Return Input' pop-up, select a reason R1 and check the checkbox 'Apply the same verified return ticket reason for the rest' Click on 'NEXT' button Click on the '3 dots' button and select 'Convert to order' Expected Result: The ticket is converted to an order Under the name of the products P1 and P2: no reason is displayed Obtained Result: The ticket is converted to an order But under the name of the products P1 and P2: the reasons still displayed (see video) | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files |  [RM-T785] Reassons displayed when convert to an Order.mp4 [^] (2,188,668 bytes) 2024-11-20 11:59 | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0172336) fdomingues (reporter) 2024-11-20 12:05 |
If I finalize the sale In Openbravo Backoffice, go to 'Sales Order' window Select the sale Go to subtab 'Lines' Select the product P1 Go to subtab 'Line Approval History' Expected Result: No line is present for the user action 'Return Ticket' Obtained Result: Line ‘Return Ticket' + line present in the 'Line Input History’ subtab with a reason |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2024-11-20 11:59 | fdomingues | New Issue | |
| 2024-11-20 11:59 | fdomingues | Assigned To | => Retail |
| 2024-11-20 11:59 | fdomingues | File Added: [RM-T785] Reassons displayed when convert to an Order.mp4 | |
| 2024-11-20 11:59 | fdomingues | Triggers an Emergency Pack | => No |
| 2024-11-20 12:05 | fdomingues | Note Added: 0172336 | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |