: Thanks so much for testing this and creating the JIRA issue!
Emma Boettcher October 2, 2020 at 6:05 PM
Holly and I have both tested this on folio-snapshot - it works except for bug noted previously.
Holly Mistlebauer October 2, 2020 at 2:49 PM
: Would you mind creating the backend circ bug for the fix we need?
The override renewal checks a list of cases for which it is allowed to override renew, the list is following:
Loan policy is not loanable; Loan policy is not renewable; Unable to calculate new due date for the loan; Loan has reached renewal limit; There is a recall request for the item; Item is aged to lost or declared lost.
We need to move 'Item is aged to lost or declared lost' above 'Loan policy is not renewable' to fix the bug I found when testing this issue.
After the bug is created, you can close this issue.
Thanks, Holly
Matt Connolly September 30, 2020 at 6:01 PM
If the item status is the sticking point here, then I recommend that we go with Bohdan's suggestion above: close this story as done and create a new backend story to address the status change (or lack thereof).
Emma Boettcher September 30, 2020 at 5:28 PM
Yes, I agree that this issue is worth solving, and if matching for declared lost or aged to lost before other failure reasons solves it, great.
I think any successful renewal (or renewal through override) should result in a status of Checked out, really, especially given our recent conversations about requiring renewals to extend due dates into the future.
SAME SCENARIOS AS WITH DECLARED LOST
Scenario
Given an item that is Aged to lost
When a user attempts to renew the item
Then fail the renewal
Renewal failure message: Item not renewed: item is Aged to lost
Allow user to override
Scenario
Given an item that is Aged to lost and has failed to renew for that reason and only that reason
When a user clicks the override button
Then display the renewal override modal
New due date: Due date will be calculated automatically
Scenario
Given an item that is Aged to lost and has failed to renew for that reason and only that reason
When a user completes the renewal override
Then:
Change the item's due date to what it would be if the item was not Aged to lost
Change the item's status to Checked out
Scenario
Given an item that was Aged to lost and was renewed
When viewing loan details
Then:
Lost field should be populated with -
corresponding row of action table should have the following values:
Action date: <date and time item was renewed>
Action: Renewed through override
Due date: <resulting due date from renewal>
Item status: Checked out
Source: <operator who renewed item>
format: Last name, firstname middlename
link to user profile
Comments: <additional information entered at renewal>