Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0034918
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 07. Sales managementmajorhave not tried2017-01-11 16:112017-03-07 16:53
ReporterplujanView Statuspublic 
Assigned Tocollazoandy4 
PrioritynormalResolutionunable to reproduceFixed in Version3.0PR17Q1
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionmainSCM revision 
Review Assigned Tomarkmm82
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0034918: [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.
TagsNo tags attached.
Attached Filespng file icon SalesOrder.png [^] (92,250 bytes) 2017-01-11 16:11

- Relationships [ Relation Graph ] [ Dependency Graph ]

-  Notes
(0094050)
markmm82 (developer)
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 (developer)
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.

- Issue History
Date Modified Username Field Change
2017-01-11 16:11 plujan New Issue
2017-01-11 16:11 plujan Assigned To => Triage Finance
2017-01-11 16:11 plujan File Added: SalesOrder.png
2017-01-11 16:11 plujan Modules => Core
2017-01-11 16:11 plujan Triggers an Emergency Pack => No
2017-01-16 20:30 markmm82 Assigned To Triage Finance => collazoandy4
2017-02-03 19:39 markmm82 Note Added: 0094049
2017-02-03 19:40 markmm82 Status new => scheduled
2017-02-03 19:44 markmm82 Note Added: 0094050
2017-02-03 19:44 markmm82 Assigned To collazoandy4 => plujan
2017-02-03 19:44 markmm82 Status scheduled => feedback
2017-02-03 19:45 markmm82 Note Deleted: 0094049
2017-02-03 19:46 markmm82 Note Edited: 0094050 View Revisions
2017-02-07 21:39 plujan Assigned To plujan => collazoandy4
2017-03-07 16:51 markmm82 Note Added: 0094801
2017-03-07 16:53 markmm82 Review Assigned To => markmm82
2017-03-07 16:53 markmm82 Status feedback => closed
2017-03-07 16:53 markmm82 Resolution open => unable to reproduce
2017-03-07 16:53 markmm82 Fixed in Version => 3.0PR17Q1

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker