[FE] Wrong expiration date displayed in Stock Management Receive page

Description

Issue discovered while executing:

Test Case: Adding new lots through Receive process

Execution Date: 03/Mar/2025

Open Execution


Reproduction steps
1. Click on the "Make Receive" button
2. Select any product and check whether the new field with the Lot Code to choose appeared
3. Click the "Lot Code" select and check whether suitable options are available in it.
4. Choose any lot code from dropdown list and click the "Add" button.
5. Choose "Add new lot" in the "Lot Code" select and click the "Add" button.
6. Enter the same lot code as previously-chosen in the "New Lot Code" field and click on the "Add" button.
7. Change the lot code to a unique one and click on the "Add" button.
8. Click the button with the new lot's code and blue pencil.
9. Make any changes in any field and click the "X" button.
10. Re-open the modal. Make any changes in any field and click the "Cancel" button.
11. Re-open the modal. Make the "Lot Code" field blank and click the "Save" button.
12. Change the lot code to a not unique one and click the "Save" button.
13. Change the lot's code to a different but unique one and click the "Save" button.
14. Re-open the modal and check whether the lot's code had been updated.
15. Click the "Expiration date" field, choose any date in the past and click the "Save" button.
16. Change the "Expiration date" to the current or future date and click the "Save" button.

 

Actual result:

Wrong expiration date is set in table row (it always shows the date one day before what the user has set). For example if user sets Expiration date 22/04/2025, in the table row we can see 21/04/2025

Attachments

2

Checklists

Activity

Show:

Dawid RuchniewiczMarch 26, 2025 at 10:51 AM

I tested it and seems that everything looks good now. Expiration date is displayed correctly. Below the video with proof:

Good job

CC:

Dawid RuchniewiczMarch 21, 2025 at 10:21 AM

Changed summary prefix to ‘FE’. Correct date is saved in database.

Artur LebiedzińskiMarch 21, 2025 at 7:57 AM
Edited

Looks like an expected state for me, we need to double check it. any thoughts here?

Artur LebiedzińskiMarch 21, 2025 at 7:55 AM

To be verified if it’s not somehow connected with the calendar calculation we discussed

Unresolved
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Original estimate

Time tracking

1d 4h 30m logged

Priority

Time Assistant

Created March 18, 2025 at 4:04 PM
Updated 3 days ago