Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0032523 | Openbravo ERP | A. Platform | public | 2016-03-21 17:59 | 2022-02-01 08:08 |
|
Reporter | inaki_garcia | |
Assigned To | Triage Platform Base | |
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | new | Resolution | open | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | pi | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | Google Chrome |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0032523: There should be a way to indicate which columns are mandatory always, despite the filtering the user may choose |
Description | There are 2 aspects that can be taken into account:
- The mandatory column headers can be marked with an asterisk (*)
- In case of filling a new record in the grid view with some missing mandatory fields/columns, the edit button tooltip error could be able to indicate what fields are missing to fill, and the actions that need to be taken. |
Steps To Reproduce | None |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | design defect | 0032522 | pi | new | Triage Platform Base | Error shown on the row edit button tooltip when inserting a row with missing mandatory fields is unreadable for a plain user |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2016-03-21 17:59 | inaki_garcia | New Issue | |
2016-03-21 17:59 | inaki_garcia | Assigned To | => Triage Finance |
2016-03-21 17:59 | inaki_garcia | Web browser | => Google Chrome |
2016-03-21 17:59 | inaki_garcia | Modules | => Core |
2016-03-21 17:59 | inaki_garcia | Triggers an Emergency Pack | => No |
2016-03-21 17:59 | inaki_garcia | Relationship added | related to 0032522 |
2016-03-22 11:22 | plujan | Web browser | Google Chrome => Google Chrome |
2016-03-22 11:22 | plujan | Assigned To | Triage Finance => platform |
2016-03-22 11:22 | plujan | Category | 02. Master data management => A. Platform |
2016-03-22 16:21 | alostale | Note Added: 0085263 | |
2016-03-22 16:21 | alostale | Assigned To | platform => inaki_garcia |
2016-03-22 16:21 | alostale | Status | new => feedback |
2016-03-23 08:42 | inaki_garcia | Note Added: 0085279 | |
2016-03-23 09:28 | inaki_garcia | Web browser | Google Chrome => Google Chrome |
2016-03-23 09:28 | inaki_garcia | Assigned To | inaki_garcia => alostale |
2016-03-23 09:28 | inaki_garcia | Status | feedback => new |
2016-03-24 08:12 | alostale | Web browser | Google Chrome => Google Chrome |
2016-03-24 08:12 | alostale | Type | defect => feature request |
2017-04-10 14:35 | alostale | Assigned To | alostale => platform |
2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
Notes |
|
|
Mandatory fields are differentiated in UI by their background color.
Please, be more concrete in the reporting (how is filtering related with this issue?); when mandatory fields are not fulfilled, an error message is shown: what do you miss here?... |
|
|
(0085279)
|
inaki_garcia
|
2016-03-23 08:42
|
|
As mentioned in the related issue, this all has to do with the Grid View. With filtering I mean removing columns to be displayed for user desired viewing reasons. If a user were to add a new record in the grid with some of the mandatory columns missing, the user should be informed to show these mandatory columns to be filled (once the columns are displayed, the red background color in the field is already shown accordingly). As for the error message shown, please refer to the related issue and check the screenshot. |
|