Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0038909 | Openbravo ERP | B. User interface | public | 2018-07-06 10:19 | 2018-08-08 13:06 |
|
Reporter | plujan | |
Assigned To | collazoandy4 | |
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | main | |
Target Version | | Fixed in Version | 3.0PR18Q4 | |
Merge Request Status | |
Review Assigned To | Sandrahuguet |
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 | 0038909: [PR18Q3] [PLM] "PLM Status" field in Product window should be renamed |
Description | As part of the project Product Lifecycle Management a new field has been added to the Product window to set the status of the product.
The label for that field is set as "PLM Status", a name that can be improved.
"PLM" as an acronym is redundant since the window is Product, and the latter part, "Status" only affects Lifecycle of the product. |
Steps To Reproduce | Open the product window and check the field as highlighted in the attached screenshot |
Proposed Solution | Check with some functional stakeholder what is a better name from an end user point of view. I've discussed it with DBA and MTR and both agree current label is not the best choice we can make. |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | PLM-StatusField.png (40,514) 2018-07-06 10:19 https://issues.openbravo.com/file_download.php?file_id=11939&type=bug

|
|
Issue History |
Date Modified | Username | Field | Change |
2018-07-06 10:19 | plujan | New Issue | |
2018-07-06 10:19 | plujan | Assigned To | => platform |
2018-07-06 10:19 | plujan | File Added: PLM-StatusField.png | |
2018-07-06 10:19 | plujan | OBNetwork customer | => No |
2018-07-06 10:19 | plujan | Modules | => Core |
2018-07-06 10:19 | plujan | Triggers an Emergency Pack | => No |
2018-07-06 11:49 | alostale | Assigned To | platform => Triage Finance |
2018-07-06 13:45 | dbaz | Note Added: 0105664 | |
2018-07-27 01:32 | collazoandy4 | Assigned To | Triage Finance => collazoandy4 |
2018-07-27 01:32 | collazoandy4 | Status | new => scheduled |
2018-07-30 16:14 | collazoandy4 | Note Added: 0106020 | |
2018-07-31 08:52 | hgbot | Checkin | |
2018-07-31 08:52 | hgbot | Note Added: 0106027 | |
2018-07-31 08:52 | hgbot | Status | scheduled => resolved |
2018-07-31 08:52 | hgbot | Resolution | open => fixed |
2018-07-31 08:52 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/070fbca94d52ff455f0c23e2b022ade6631cb20c [^] |
2018-07-31 08:52 | Sandrahuguet | Review Assigned To | => Sandrahuguet |
2018-07-31 08:52 | Sandrahuguet | Note Added: 0106028 | |
2018-07-31 08:52 | Sandrahuguet | Status | resolved => closed |
2018-07-31 08:52 | Sandrahuguet | Fixed in Version | => 3.0PR18Q4 |
2018-07-31 10:33 | hgbot | Checkin | |
2018-07-31 10:33 | hgbot | Note Added: 0106034 | |
2018-08-08 13:06 | hudsonbot | Checkin | |
2018-08-08 13:06 | hudsonbot | Note Added: 0106234 | |