[FOLIO-2473] When requester barcode is changed in Users, requests should update accordingly Created: 12/Nov/19  Updated: 29/Aug/23  Resolved: 29/Aug/23

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Tech Debt Priority: P2
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: backend, tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UIREQ-673 "Sort results by barcode" does not so... Closed
Cloners
clones UIREQ-650 [BE] When inventory data (e.g. barcod... Open
Relates
relates to CIRC-1139 Request pick up notice not sent to re... Closed
relates to UIU-1370 Link from Users to Requests Doesn't W... Closed
relates to CHAL-145 Users has 1 open requests, but no req... Closed
relates to UXPROD-2594 After an item has been associated wit... Draft
relates to UXPROD-3399 When Relevant User Record Attributes ... Draft
Sprint: Prokopovych - Sprint 129
Development Team: Vega

 Description   

Steps to repro:

  1. log into snapshot
  2. Go to users and find a user
  3. Create a request for that user
  4. Back in users, change the users barcode
  5. Now go back to Requests and look at the users requests

Expected:

  • In the results list, the requester barcode should be updated to new barcode
  • On request details, the requester barcode should be updated to new barcode

Actual:

  • Requester barcode not updated in results list
  • Requester barcode not updated on detail record


 Comments   
Comment by Holly Mistlebauer [ 27/Aug/21 ]

Waiting for decision from App Interaction group...otherwise we could end up doing re-work...we also don't have the capacity...

Comment by Anya [ 13/Dec/21 ]

SUPPORT: what is causing this block - we have an open bug on this, which is blocked by this. 

CC Holly Mistlebauer and Martina.Schildt

Comment by Marc Johnson [ 13/Dec/21 ]

Anya

what is causing this block - we have an open bug on this, which is blocked by this.

This is blocked on FOLIO making a decision on how cross app data sync is intended to work.

It could be unblocked prior to that, however that would increase the change of needing necessary rework if the work is not aligned with this decision.

cc: Holly Mistlebauer Martina.Schildt

Comment by Holly Mistlebauer [ 13/Dec/21 ]

Marc Johnson: Thanks for the update...

Comment by Marc Johnson [ 06/Jan/22 ]

Holly Mistlebauer Stephanie Buck

Given the switch in module ownership, should this be moved to Vega (and removed from the current sprint)?

Comment by Holly Mistlebauer [ 07/Jan/22 ]

Marc Johnson: Thanks for pointing this out. I have reassigned this JIRA to Vega.

Comment by Stephanie Buck [ 27/May/22 ]

Alexander Kurash , can you take a look at this ticket and let me know what I can do to help unblock it? Thanks!

 

Comment by Marc Johnson [ 27/May/22 ]

Stephanie Buck

can you take a look at this ticket and let me know what I can do to help unblock it?

The context I shared in my comment above is still true.

This is blocked on FOLIO making a decision on how cross app data sync is intended to work.

It could be unblocked prior to that, however that would increase the change of needing necessary rework if the work is not aligned with this decision.

The cross-app sync working group has been trying to define the community wide guidance for this area. It is close to having completed this endeavour.

The proposed guidance does not differ significantly from the way that the inventory search implementation achieves this synchronisation and other areas, e.g. circulation log and remote storage I think, have also followed suite.

Practically, I think that means this work is unblocked, as the way this would be implemented is understood at this point.

It will need work in mod-users to publish that a user record has changed before this issue can be worked on.

cc: Martina.Schildt Brooks Travis Raman Auramau Zak Burke Owen Stephens Charlotte Whitt

Comment by Stephanie Buck [ 29/Aug/23 ]

Very old ticket. 

Generated at Thu Feb 08 23:20:54 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.