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

CHECKOUT_4 or CHECKOUT_5 does not work as expected. #1379

Closed
pronguen opened this issue Nov 4, 2020 · 1 comment
Closed

CHECKOUT_4 or CHECKOUT_5 does not work as expected. #1379

pronguen opened this issue Nov 4, 2020 · 1 comment
Assignees
Labels
bug Breaks something but is not blocking f: circulation Concerns the circulation interface or backend needs info p-High High priority (to be solved in the 2-3 next months)
Milestone

Comments

@pronguen
Copy link
Contributor

pronguen commented Nov 4, 2020

Describe the bug

I have an item in transit. It is requested by patron A. It is checked out for this patron without reception at desk. This situation leads to a problem:

  1. either the request seems not to have been validated (if it was in transit to house). Consequence: it still appears in the requests.
  2. or I have an red error message (see screenshot)

To Reproduce

Case 1

  1. Take an item in transit to house
  2. Add a request on it for patron A
  3. Check out the item for patron A
  4. See tab "Requests" of patron A
  5. See item detailed view

Case 2

  1. Take an item on loan by patron X
  2. Add a request on it for patron A
  3. Checkin the item so that it goes in transit for pickup
  4. Check out the item for patron A
  5. See error message

Expected behavior

At the checkout, the loan is automatically validated and received, so that it does not appear as a request anymore.

Context

Proposed by pilot libraries

Screenshots

Case 1: there are now 2 loans for the same patron:
image

Case 2: error message
image

@pronguen pronguen added f: circulation Concerns the circulation interface or backend triage bug Breaks something but is not blocking p-High High priority (to be solved in the 2-3 next months) labels Nov 4, 2020
@iGormilhit iGormilhit added this to the v1.0.0 milestone Nov 26, 2020
@BadrAly
Copy link

BadrAly commented Jan 6, 2021

No longer a problem

@BadrAly BadrAly closed this as completed Jan 6, 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 needs info p-High High priority (to be solved in the 2-3 next months)
Projects
None yet
Development

No branches or pull requests

3 participants