Openbravo Issue Tracking System - POS2
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0047204POS2Restaurantspublic2021-06-22 17:192021-06-23 12:56
ReporterYBataille 
Assigned ToRetail 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed 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 PackNo
Summary0047204: JIRA 2038 - Ticket / Duplicata - Button should be grayed
Description You must not be able to print a duplicate ticket until the sale/ticket is completed. Actually, we can . It should be impossible and button should be grayed
Steps To ReproduceStart a new order on the POS.
Button 'Duplicata' is grayed
Add one item
Button 'Duplicata' is accessible
It Could not
Proposed Solutionset this 'duplicata' button unable, until at least One ticket has been printed. Or until payment is done.
But this button should be grayed.
Additional Information
TagsNo tags attached.
Relationships
Attached Filespng Duplicata Grayed 2021-06-22.png (61,769) 2021-06-22 17:19
https://issues.openbravo.com/file_download.php?file_id=15955&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2021-06-22 17:19YBatailleNew Issue
2021-06-22 17:19YBatailleAssigned To => Retail
2021-06-22 17:19YBatailleFile Added: Duplicata Grayed 2021-06-22.png
2021-06-22 17:19YBatailleTriggers an Emergency Pack => No
2021-06-22 17:20YBatailleNote Added: 0129728
2021-06-23 12:56dmiguelezNote Added: 0129739
2021-06-23 12:56dmiguelezStatusnew => closed
2021-06-23 12:56dmiguelezResolutionopen => no change required

Notes
(0129728)
YBataille   
2021-06-22 17:20   
JIRA number is 2138
(0129739)
dmiguelez   
2021-06-23 12:56   
The system is behaving as expected.

In this case the Ticket printed should have a label stating that is is a 'DRAFT' Ticket (if necessary, this should be managed in the custom ticket template)

From a functional point of view, it is ok to print a Draft ticket as many times as necessary, as long as the template clearly states that it is a draft ticket.

If this is required by the client, the json configuration file for the behavior of the button can be customized (however, we do not recommend it)