Current Behaviour
On the Product Audit page, under the "Active Purchase Order" tab, the list of Purchase Orders and the Timeline are displaying incorrect data:
- List Visibility: A cancelled PO is still appearing in the "Active" list, while other genuinely active POs are completely missing and cannot be viewed.
- Timeline Accuracy: The timeline section only displays the cancelled PO. Furthermore, it incorrectly shows this PO in a "Created" status rather than "Cancelled," and completely fails to show the timeline events for the active POs.
(Note: The Total ATP calculation is functioning correctly and successfully deducts the cancelled quantity, indicating this is likely a UI filtering/display issue rather than a backend calculation error).
Expected Behaviour
- The "Active Purchase Order" list should strictly filter out cancelled POs and display all currently active POs for that product.
- The Timeline section should display events for all relevant POs, and if a cancelled PO is shown, its status must accurately reflect as "Cancelled."
Steps to Reproduce
- Navigate to the Purchase Order page.
- Create three separate Purchase Orders (POs) for a single product.
- Cancel one of the three POs (leave the other two active).
- Navigate to the Audit tab and open the Product Detail page for that specific product.
- Go to the Active Purchase Order section.
- Observe the PO list: Note that the only PO created first is visible , but the two active POs are missing.
- Observe the Timeline section: Note that only the cancelled PO is shown, and its status is incorrectly listed as "Created."
- Observe the Total ATP: Note that it correctly reflects the inventory without the cancelled PO quantity.
Screenshots and Jam Video
Jam video -https://jam.dev/c/dfe0c5b7-e6e4-491d-aca7-f38de37134b6
Current Behaviour
On the Product Audit page, under the "Active Purchase Order" tab, the list of Purchase Orders and the Timeline are displaying incorrect data:
(Note: The Total ATP calculation is functioning correctly and successfully deducts the cancelled quantity, indicating this is likely a UI filtering/display issue rather than a backend calculation error).
Expected Behaviour
Steps to Reproduce
Screenshots and Jam Video
Jam video -https://jam.dev/c/dfe0c5b7-e6e4-491d-aca7-f38de37134b6