Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0039437 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
design defect | [Openbravo ERP] B. User interface | minor | have not tried | 2018-10-11 13:13 | 2022-02-01 08:07 | |||||||
Reporter | plujan | View Status | public | |||||||||
Assigned To | Triage Platform Base | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | main | SCM revision | ||||||||||
Review Assigned To | ||||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0039437: [PR18Q4] Error message after a wrong entered value does not disappear when values are fixed | |||||||||||
Description | When trying to create an incomplete Sales Order line, an expected error message is shown. But after the data is corrected and the record successfully saved, the error message does not disappear. | |||||||||||
Steps To Reproduce | 1. Enter as F&B admin 2. Open Sales Order window 3. Create a new header with valid data 4. Focus the Lines tab and click the "new in form" button. 5. Do not complete any data and change the focus back to the header 6. As expected, a red message in the line will alert the user of the missing data. 7. Return to the line and complete the data. Note that after saving the error message is not removed (see attached screenshot) 8. Complete the Sales Order. Note the message is still there. 9. Create a new Sales Order header. Note the message still there. 10. Create a new Line. Note the message still there. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ErrorSalesOrderLine.png [^] (84,761 bytes) 2018-10-11 13:13
| |||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |||||||||||||||
|
Notes | |
(0107613) alostale (manager) 2018-10-26 10:43 |
Moving to design defect: currently, messages are designed to be removed only after user closes them; there is no way to define any other automatic mechanism to close them. DBA: can you comment on how this should behave? |
(0107631) dbaz (developer) 2018-10-29 10:23 edited on: 2019-09-17 11:19 |
If in the header you leave a mandatory field empty, and you move to the child, an error is shown in the header. If you go back to the header, and start editing, the message dissapears. The same behavior should apply in the opposite case, which is the one reported in the issue. |
Issue History | |||
Date Modified | Username | Field | Change |
2018-10-11 13:13 | plujan | New Issue | |
2018-10-11 13:13 | plujan | Assigned To | => platform |
2018-10-11 13:13 | plujan | File Added: ErrorSalesOrderLine.png | |
2018-10-11 13:13 | plujan | Modules | => Core |
2018-10-11 13:13 | plujan | Triggers an Emergency Pack | => No |
2018-10-26 10:43 | alostale | Note Added: 0107613 | |
2018-10-26 10:43 | alostale | Type | defect => design defect |
2018-10-26 10:44 | alostale | Assigned To | platform => dbaz |
2018-10-26 10:44 | alostale | Status | new => feedback |
2018-10-29 10:23 | dbaz | Note Added: 0107631 | |
2018-10-31 18:38 | dbaz | Status | feedback => new |
2019-02-22 12:44 | alostale | Relationship added | related to 0040179 |
2019-09-17 11:19 | dbaz | Note Edited: 0107631 | View Revisions |
2019-09-17 12:37 | gorkaion | Issue cloned | 0041821 |
2019-09-17 12:37 | gorkaion | Relationship added | related to 0041821 |
2019-09-17 13:03 | dbaz | Assigned To | dbaz => platform |
2022-02-01 08:07 | alostale | Assigned To | platform => Triage Platform Base |
Copyright © 2000 - 2009 MantisBT Group |