Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0034918Openbravo ERP07. Sales managementpublic2017-01-11 16:112017-03-07 16:53
Reporterplujan 
Assigned Tocollazoandy4 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionunable to reproduce 
PlatformOS5OS Version
Product Versionmain 
Target VersionFixed in Version3.0PR17Q1 
Merge Request Status
Review Assigned Tomarkmm82
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0034918: [PR17Q1] [AUoM] Alternate Unit of Measure adds a hidden mandatory field
DescriptionWhen creating a new Sales Order with the Alternate Unit of Measure feature enabled, the regular field "Ordered Quantity" (mandatory) is greyed out.

There is not a single hint that the field is now calculated and that the "new" mandatory field is located far below in the form.

"Operative Quantity" is marked as a regular (non mandatory) field but it is actually replacing the Ordered Quantity field.
Steps To ReproduceTry to create a new Sales Order with the Alternate Unit of Measure enabled.

See the above described problems in the attached screenshot.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Filespng SalesOrder.png (92,250) 2017-01-11 16:11
https://issues.openbravo.com/file_download.php?file_id=10284&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2017-01-11 16:11plujanNew Issue
2017-01-11 16:11plujanAssigned To => Triage Finance
2017-01-11 16:11plujanFile Added: SalesOrder.png
2017-01-11 16:11plujanModules => Core
2017-01-11 16:11plujanTriggers an Emergency Pack => No
2017-01-16 20:30markmm82Assigned ToTriage Finance => collazoandy4
2017-02-03 19:39markmm82Note Added: 0094049
2017-02-03 19:40markmm82Statusnew => scheduled
2017-02-03 19:44markmm82Note Added: 0094050
2017-02-03 19:44markmm82Assigned Tocollazoandy4 => plujan
2017-02-03 19:44markmm82Statusscheduled => feedback
2017-02-03 19:45markmm82Note Deleted: 0094049
2017-02-03 19:46markmm82Note Edited: 0094050bug_revision_view_page.php?bugnote_id=0094050#r14467
2017-02-07 21:39plujanAssigned Toplujan => collazoandy4
2017-03-07 16:51markmm82Note Added: 0094801
2017-03-07 16:53markmm82Review Assigned To => markmm82
2017-03-07 16:53markmm82Statusfeedback => closed
2017-03-07 16:53markmm82Resolutionopen => unable to reproduce
2017-03-07 16:53markmm82Fixed in Version => 3.0PR17Q1

Notes
(0094050)
markmm82   
2017-02-03 19:44   
(edited on: 2017-02-03 19:46)
This issue is not reproducible neither on PI or PR17Q1 backport anymore. Please confirm if it is already fixed or there is anything else to add before reject the issue.
(0094801)
markmm82   
2017-03-07 16:51   
After several tests and discussions it looks like this issues is caused by a partial update to 17Q1 version. We tried in an environment with 3.0PR16Q4 version and then updating it to 3.0PR17Q1 (updating from the latest changes in https://code.openbravo.com/erp/backports/3.0PR17Q1 [^]) and all concerned to the described bugs seems to be working as expected. It is not reproducible in pi neither. Due that, this issue will be closed and if a customer reports this issue in the future then we should fix in his environment analyzing particularities of his repository status.