Loans: Support Bulk Renew on Loans

Description

Purpose: The Loans page should support bulk actions such as Claim returned, Renew, Change due date etc. The purpose of this story is to implement the mechanism for bulk select and our first bulk action (renew).

Scenarios:

  1. Scenario

    • Given the Loans page, Open Loans view

    • When displayed

    • Then each open loan row should be accompanied by a checkbox (default unchecked) as shown in the below linked wireframe

  2. Scenario

    • Given the checkbox column on the Loans page, Open Loans view

    • When displayed

    • Then the column header should contain a checkbox (default unchecked)

  3. Scenario

    • Given the column header checkbox

    • When checked

    • Then all the rows below should also be checked (it should still be possible to uncheck individual rows)

  4. Scenario

    • Given the column header checkbox

    • When unchecked

    • Then all the rows below should also be unchecked (it should still be possible to individually re-check individual rows)

  5. Scenario

    • Given the Loans page

    • When displayed

    • Then a Renew button should display at the top of the page as shown in the below linked wireframe

  6. Scenario

    • Given one or more loan rows is checked on the Loans page

    • When the Renew button is clicked

    • Then the selected/checked loans should be renewed according to the basic logic outlined in (eventually we'll look to the loan policy for renewal period, but this is just an early iteration)

Out of scope for this story (need UX guidance on patterns):

  • Success confirmation message

  • Error message if you try to renew without selecting a loan

Mock-Up: https://www.dropbox.com/s/owyyqih5euj12jt/loan-history-open-4.png?dl=0

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Cate Boerema October 6, 2017 at 6:26 PM

Okay will do! Thanks.

Michal Kuklis October 6, 2017 at 6:22 PM

I haven't touched the actual renew functionality in this issue (I just use it to renew multiple items) but I do see the time (not date) being changed every time I renew an item by couple seconds. Should the previous date be pushed for another 30 days? For example:

10/06/2017 exec renew
11/06/2017 exec renew
12/06/207 ...

If so it should be easy to fix. Perhaps we can create a bug for it and close this one?

Cate Boerema October 6, 2017 at 6:15 PM

Hi , this seems to be working pretty well, but I notice that only the first renewal pushes out the due date. That was definitely not the intention of the renewal feature described in . Since Charlotte tested that one, I don't know if this is a regression or if it was never pushing out the due date with every renewal. Do you know?

Michal Kuklis October 2, 2017 at 2:33 PM

The work on this should be now done but it hasn't been merged yet.

Done

Details

Assignee

Reporter

Priority

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 12, 2017 at 12:25 PM
Updated November 22, 2017 at 4:57 PM
Resolved October 6, 2017 at 6:26 PM
TestRail: Cases
TestRail: Runs