Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0054549 | Openbravo ERP | 03. Procurement management | public | 2024-02-01 21:16 | 2024-02-13 08:28 |
| Reporter | andrea_lopez | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | normal | Severity | major | 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 | 0054549: Requisition - Inconsistency in the read-only logic for certain fields between the Requisition and Manage Requisition interfaces | ||||
| Description | The Read Only Logic for certain fields in the Tab Lines of the Manage Requisition Window isn't functioning properly. When the Requisition status is set to Completed or Closed, certain fields should be restricted to read-only mode, mirroring the behavior in the Requisition window. Both Manage Requisition and Requisition utilize the same table, thus the read-only logic should be consistent across both interfaces. However, it appears to be functioning correctly only in the Requisition window. | ||||
| Steps To Reproduce | 1.- Create a new Requisition. 2.- Add a new line to the requisition, specifying a Product, Need by Date, and Operative Quantity. 3.-Proceed to complete the Requisition. 4.-Upon completion, certain fields within the line should become read-only, including Business Partner, Price List, Quantity, and UOM. This same read-only logic should be consistent across both the Requisition and Manage Requisition interfaces. 5.-However, upon opening the Manage Requisition interface, it's observed that these fields are not rendered as read-only as expected. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2024-02-01 21:16 | andrea_lopez | New Issue | |||
| 2024-02-01 21:16 | andrea_lopez | Assigned To | => Triage Omni OMS | ||
| 2024-02-01 21:16 | andrea_lopez | Modules | => Core | ||
| 2024-02-01 21:16 | andrea_lopez | Triggers an Emergency Pack | => No | ||
| 2024-02-13 08:28 | vmromanos | Assigned To | Triage Omni OMS => Triage Platform Base | ||
| There are no notes attached to this issue. |