[UIIN-1656] Item administrative data mismatched in view and edit mode Created: 29/Sep/21  Updated: 03/Mar/22  Resolved: 01/Dec/21

Status: Closed
Project: ui-inventory
Components: None
Affects versions: None
Fix versions: 9.0.0

Type: Bug Priority: P3
Reporter: Molly Driscoll Assignee: Michal Kuklis
Resolution: Done Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Skærmbillede 2021-12-01 kl. 16.02.43.png     PNG File Skærmbillede 2021-12-01 kl. 16.03.12.png     PNG File Skærmbillede 2021-12-01 kl. 16.04.05.png     PNG File item_editmode.PNG     PNG File item_viewmode.PNG    
Sprint: Prokopovych - Sprint 128
Story Points: 3
Development Team: Prokopovych
Release: Lotus R1 2022
Affected Institution:
Okanagan College
Tester Assignee: Charlotte Whitt

 Description   

Overview: When accessing an item record in the Inventory app, if you view the administrative data (created and updates dates, times, and sources) in view mode, you see conflicting data than you see in edit mode of the same item record.

Steps to Reproduce:

  1. Log into https://folio-juniper.dev.folio.org/ 
  2. Open the Inventory app.
  3. Find an item record and click on the barcode to open the item record in view mode.
  4. Expand the record last updated section and note the information there.
  5. Edit the item record and save.
  6. Expand the record last updated section and note the information there. The record last updated information should have changed.
  7.  Edit the record.
  8. Expand the record last updated section and note the information there.

Expected Results: It should match what you see in step 6.
Actual Results: The information is different in view and edit mode.

Additional Information: Originally reported by Okanagan College (Iris Hotfix 3.2), but replicated on a Juniper tenant.
URL:
Interested parties: Greg Hutton



 Comments   
Comment by Anya [ 04/Oct/21 ]

SUPPORT: time and day wrong -could the ui be grabbing things from different places ...

Comment by Charlotte Whitt [ 11/Oct/21 ]

Anya Molly Driscoll - this sounds to me as a cache problem.

Have you tested if this behavior is seen in other apps using the metadata component, e.g. Orders, Users etc.?

CC: Zak Burke Michal Kuklis

Comment by Molly Driscoll [ 13/Oct/21 ]

Charlotte Whitt I could not replicate this behavior in the Users app. I tried in the Orders app, but the metadata is not visible in the edit mode on a pending order. Both of my tests were done in https://folio-juniper.dev.folio.org/ 

Comment by Anya [ 01/Nov/21 ]

Support : Michal Kuklis could you help Support triage this ticket? Thanks.

Comment by Michal Kuklis [ 01/Nov/21 ]

Anya that actually looks good to me. When you expend the record last updated the value under there shows the date when the record was originally created (not updated). The label is: "Record created". The accordion's header shows the date the record was updated. 

Comment by Anya [ 08/Nov/21 ]

Support : Molly Driscoll please answer Michal Kuklis

Comment by Molly Driscoll [ 08/Nov/21 ]

Michal Kuklis I'm not sure I understand. The data is both for created and updated. The created data is consistent in both edit and view mode, but the updated data varies between the two views. 

Comment by Michal Kuklis [ 08/Nov/21 ]

Molly Driscoll you are right. I was looking at the wrong place. I was finally able to reproduce it. This is definitely a bug.

Comment by Molly Driscoll [ 08/Nov/21 ]

Thanks so much Michal Kuklis; appreciate the follow-up! Tagging Anya for Support SIG awareness.

Comment by Charlotte Whitt [ 22/Nov/21 ]

Oleksiy_Lemeshko and Holly Mistlebauer - in the Support SIG meeting today 11/22/2021 we talked about having the bug assigned to our next sprint; while it has ben reviewed by Michal Kuklis

Comment by Charlotte Whitt [ 01/Dec/21 ]

Manual test in https://folio-juniper.dev.folio.org/

It works as expected, and I'll close the ticket. Thanks Michal Kuklis

Generated at Thu Feb 08 22:22:00 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.