Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Availability notification: wrong pick-up location name #2295

Closed
pronguen opened this issue Aug 12, 2021 · 0 comments · Fixed by #2297
Closed

Availability notification: wrong pick-up location name #2295

pronguen opened this issue Aug 12, 2021 · 0 comments · Fixed by #2297
Assignees
Labels
bug Breaks something but is not blocking f: circulation Concerns the circulation interface or backend f: notifications p-High High priority (to be solved in the 2-3 next months)

Comments

@pronguen
Copy link
Contributor

Describe the bug

Availability notification: wrong pick-up location name

To Reproduce

  1. Take an item
  2. Add a request for patron A, pick-up library A
  3. Add a request for patron B, pick-up library B
  4. Check-out the item for A
  5. Check-in the item
  6. See that patron B receives an availability notification, with pick-up library A instead of B

Expected behavior

Pick-up library is correct.

Context

  • server: ils.test.rero.ch
  • version: v1.4.6
  • not solved by 1.4.7 as deployed on 12.08.21 on ilsdev
@pronguen pronguen added f: circulation Concerns the circulation interface or backend f: notifications bug Breaks something but is not blocking p-High High priority (to be solved in the 2-3 next months) labels Aug 12, 2021
@pronguen pronguen mentioned this issue Aug 12, 2021
7 tasks
rerowep added a commit to rerowep/rero-ils that referenced this issue Aug 17, 2021
rerowep added a commit that referenced this issue Aug 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Breaks something but is not blocking f: circulation Concerns the circulation interface or backend f: notifications p-High High priority (to be solved in the 2-3 next months)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants