Openbravo Issue Tracking System - Openbravo ERP | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0037041 | Openbravo ERP | B. User interface | public | 2017-10-10 10:38 | 2022-02-28 13:54 |
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 | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | |||||
Web browser | |||||
Modules | Core | ||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0037041: [PR17Q4] [AWO] The use of acronym "AWO" should be avoided in the user interface | ||||
Description | Unlike other terms like UOM that are industry standards, AWO is an internal naming for a project. No end user will understand it (in the best case) or it can be misunderstood. An example of this is the module named "Openbravo AWO Retail Connector" | ||||
Steps To Reproduce | Browse the "Add modules" tab of available modules. | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2017-10-10 10:38 | plujan | New Issue | |||
2017-10-10 10:38 | plujan | Assigned To | => Triage Finance | ||
2017-10-10 10:38 | plujan | Modules | => Core | ||
2017-10-10 10:38 | plujan | Triggers an Emergency Pack | => No | ||
2022-02-28 13:54 | vmromanos | Assigned To | Triage Finance => Triage Omni WMS |
There are no notes attached to this issue. |