Project:
| View Revisions: Issue #54568 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0054568: [24Q1] Return Line Reason is set as "undefined" if no input is chosen | ||
| Revision | 2024-02-02 15:46 by lorenzofidalgo | ||
| Description | At the moment of selecting values in a Return Line, if the POS2 user chooses to insert no input, "undefined" is shown as value inside the ticket instead of an empty value or other proper solution. This issue has been reproducible in 24Q1 (QA status) and it seems to come from the development that extends the Return Reason functionality. In older versions, the flows differ slightly but, now, the POS2 user receives a wrong value that was not shown previously. Issue not reproducible in livebuilds 23Q4.1. |
||
| Revision | 2024-02-02 15:46 by lorenzofidalgo | ||
| Description | At the moment of selecting values in a Return Line, if the POS2 user chooses to insert no input, "undefined" is shown as value inside the ticket instead of an empty value or other proper solution. This issue has been reproducible in 24Q1 (QA status) and it seems to come from the development that extends the Return Reason functionality. In older versions, the flows differs slightly but, now, the POS2 user receives a wrong value that was not shown previously. Issue not reproducible in livebuilds 23Q4.1. |
||
| Revision | 2024-02-02 15:43 by lorenzofidalgo | ||
| Description | At the moment of selecting values in a Return Line, if the POS2 user chooses to insert no input, "undefined" is shown as value inside the ticket instead of an empty value or other proper solution. This issue has been reproducible in 24Q1 (QA status) and it seems to come from the developemnt that extends the Return Reason functionality. In older versions, the flows differs slightly but, now, the POS2 user receives a wrong value that was not shown previously. Issue not reproducible in livebuilds 23Q4.1. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |