Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0036450 | Openbravo ERP | 04. Warehouse management | public | 2017-07-10 13:49 | 2017-07-10 13:49 |
| Reporter | plujan | ||||
| Assigned To | Triage Omni WMS | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | main | ||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | No | ||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0036450: [PR17Q3] Alternate Unit of Measure config checks differs leaving a non consistent GUI | ||||
| Description | Preference for activating the alternate UoM feature makes two things, show the new quantity and uom fields and disabled the standard ones. In case of a misconfiguration of this preference, the new fields are not shown while the standard ones are kept disabled, effectively turning off the transactional windows. See steps. | ||||
| Steps To Reproduce | Scenario A (working as expected): 1. On a system without the preference of alternate UoM (or with the preference set to N), go to Purchase Order or Goods Receipt window. 2. Create a new line for an item, check that there are no fields for the alternate unit and the standard ones are enabled. Scenario B (also working as expected): 1. On a system with the preference of alternate UoM set to Y and all the other values properly configured, go to Purchase Order or Goods Receipt window. 2. Create a new line for an item, check that there are specific fields for the alternate unit and the standard ones are disabled. Scenaro C (not working as expected) 1. On a system with the preference of alternate UoM set to Y and the filter of user set to Openbravo user, go as Openbravo to Purchase Order or Goods Receipt window. 2. Create a new line for an item, check that there are not specific fields for the alternate unit and the standard ones are disabled, so no value can be set. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2017-07-10 13:49 | plujan | New Issue | |||
| 2017-07-10 13:49 | plujan | Assigned To | => Triage Finance | ||
| 2017-07-10 13:49 | plujan | OBNetwork customer | => No | ||
| 2017-07-10 13:49 | plujan | Modules | => Core | ||
| 2017-07-10 13:49 | plujan | Triggers an Emergency Pack | => No | ||
| There are no notes attached to this issue. |