Openbravo Issue Tracking System - Openbravo ERP | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0048531 | Openbravo ERP | A. Platform | public | 2022-02-04 10:26 | 2022-02-04 10:26 |
Reporter | ibrahim_hammani | ||||
Assigned To | Triage Platform Base | ||||
Priority | normal | Severity | trivial | Reproducibility | always |
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 | 0048531: Reports compilation on testing is hard to debug | ||||
Description | When an error occures in the reports compilation we don't have enough informations about the buggy report. please see: org.openbravo.test.reporting.AllJrxmlCompilation.jrxmlShouldCompile(AllJrxmlCompilation.java:67) I suggest to display at least the buggy report's path | ||||
Steps To Reproduce | Use any invalid report then run the test: org.openbravo.test.reporting.AllJrxmlCompilation.jrxmlShouldCompile | ||||
Proposed Solution | I suggest to display at least the buggy report's path | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2022-02-04 10:26 | ibrahim_hammani | New Issue | |||
2022-02-04 10:26 | ibrahim_hammani | Assigned To | => Triage Platform Base | ||
2022-02-04 10:26 | ibrahim_hammani | Modules | => Core | ||
2022-02-04 10:26 | ibrahim_hammani | Triggers an Emergency Pack | => No |
There are no notes attached to this issue. |