Openbravo Issue Tracking System - Openbravo ERP | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0041822 | Openbravo ERP | B. User interface | public | 2019-09-17 12:41 | 2023-07-04 12:35 | |||||||
Reporter | gorkaion | |||||||||||
Assigned To | Triage Platform Base | |||||||||||
Priority | high | Severity | minor | Reproducibility | have not tried | |||||||
Status | acknowledged | Resolution | open | |||||||||
Platform | OS | 5 | OS Version | |||||||||
Product Version | main | |||||||||||
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 | 0041822: Messages in header tab should include the process that has generated the message | |||||||||||
Description | Once you complete a process, the message displays "Process completed successfully", but you don't know which is the process it has launched this message. The problem for the user is: if he continue surfing the SO and its childs, just after executing a process that has generated this message, once he backs to the header, he view the message, but he does not have a clear idea of which processes generated it. The solution is to change «Process completed successfully» by «"Copy From" completed successfully» (note the quotes in the process name) | |||||||||||
Steps To Reproduce | 1. Enter as F&B admin 2. Open Sales Order window 3. Create a new header with valid data in form view 4. Click in Copy Lines button 5. Select at least 1 product and click OK 6. As expected, a green message in the header is shown with the number of copied products and «Process completed successfully» in the title | |||||||||||
Proposed Solution | ||||||||||||
Additional Information | ||||||||||||
Tags | No tags attached. | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
Issue History | ||||||||||||
Date Modified | Username | Field | Change | |||||||||
2019-09-17 12:41 | gorkaion | New Issue | ||||||||||
2019-09-17 12:41 | gorkaion | Assigned To | => dbaz | |||||||||
2019-09-17 12:41 | gorkaion | Modules | => Core | |||||||||
2019-09-17 12:41 | gorkaion | Resolution time | => 1570485600 | |||||||||
2019-09-17 12:41 | gorkaion | Triggers an Emergency Pack | => No | |||||||||
2019-09-17 12:41 | gorkaion | Issue generated from | 0041821 | |||||||||
2019-09-17 12:41 | gorkaion | Relationship added | related to 0041821 | |||||||||
2019-09-17 13:03 | dbaz | Assigned To | dbaz => platform | |||||||||
2019-09-17 13:35 | AugustoMauch | Assigned To | platform => jarmendariz | |||||||||
2019-09-17 13:35 | AugustoMauch | Status | new => scheduled | |||||||||
2019-09-17 16:17 | rafaroda | Issue Monitored: rafaroda | ||||||||||
2019-09-27 11:06 | alostale | Assigned To | jarmendariz => platform | |||||||||
2019-09-27 11:06 | alostale | Severity | major => minor | |||||||||
2019-09-27 11:06 | alostale | Status | scheduled => acknowledged | |||||||||
2019-09-27 11:06 | alostale | Type | defect => design defect | |||||||||
2022-02-01 08:07 | alostale | Assigned To | platform => Triage Platform Base |
There are no notes attached to this issue. |