[UXPROD-3168] prepopulate start date field when adding additional fixed due date schedule date range Created: 21/Jun/18  Updated: 26/Oct/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Adam Shire Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: circ_po_small, loans
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Development Team: None
Rank: Cornell (Full Sum 2021): R3

 Description   

Purpose:
To help prevent users from creating fixed due date schedules with gaps between date ranges

Justification:
Fixed due date schedules should not contain gaps between date ranges. If gaps exist, a checkout or renewal occurring on a date falling in a gap will result in an error message and loan/renewal will not happening.

Scenario 1 :
GIVEN a fixed due date schedule with one or more date ranges already defined
WHEN the "add" button is clicked to add a new date range
THEN the new date range's start date field should prepopulate using the previous range's end date + 1 day

Scenario 2:

GIVEN a fixed due date schedule with gaps between two date ranges
WHEN the save button is clicked
THEN an error message is displayed saying "Due date ranges must not contain gaps"
AND saving is prevented

example:
range 1
start date 6/1/2018
end date 7/1/2018
due date 9/1/2018

'click add'

range 2
start date is prepopulated with 7/2/2018



 Comments   
Comment by Adam Shire [ 21/Jun/18 ]

Cate Boerema here's the user story.

Comment by Erin Nettifee [ 07/Jul/21 ]

Moving this to a feature so it could be viewed and ranked, since this has not been implemented

Comment by Thomas Trutt [ 26/Oct/23 ]

If implemented i feel that this should be a warning and not a hard block. 

Generated at Fri Feb 09 00:29:52 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.