Openbravo Issue Tracking System - Modules |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0054499 | Modules | Openbravo Business API | public | 2024-01-30 11:28 | 2024-01-30 11:29 |
|
| Reporter | caristu | |
| Assigned To | Triage Platform Conn | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Regression date | |
| Regression introduced by commit | |
| Regression level | |
| Review Assigned To | |
| Support ticket | |
| OBNetwork customer | No |
| Regression introduced in release | |
|
| Summary | 0054499: Mechanism to avoid property mapping definitions causing incorrect module dependencies |
| Description | It would be nice to have a mechanism to ensure/detect wrong property mapping definitions that can lead to wrong cross dependency definition between modules, like in the case detected in 0054498 |
| Steps To Reproduce | See issue 0054498 |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0054498 | | closed | Retail | Modules | Cross dependency to org.openbravo.retail.discounts | | related to | feature request | 0048626 | | acknowledged | caristu | Retail Modules | Create a mechanism to detect API changes in the Openbravo Business API |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2024-01-30 11:28 | caristu | New Issue | |
| 2024-01-30 11:28 | caristu | Assigned To | => Triage Platform Conn |
| 2024-01-30 11:28 | caristu | OBNetwork customer | => No |
| 2024-01-30 11:28 | caristu | Issue generated from | 0054498 |
| 2024-01-30 11:28 | caristu | Relationship added | related to 0054498 |
| 2024-01-30 11:28 | caristu | Status | new => acknowledged |
| 2024-01-30 11:29 | caristu | Relationship added | related to 0048626 |