Expiration date should not be required when setting up a patron block

Description

While testing the Q4 2018 release at http://folio-snapshot.aws.indexdata.com, Holly was forced to enter an Expiration Date when setting up a patron block (see attached mock-up). Expiration Date is not a required field. Until this is fixed, Chalmers should enter a year of 9999 when they want the block to not expire.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Holly MistlebauerDecember 19, 2018 at 9:01 PM

Holly tested this on http://folio-q4-core.aws.indexdata.com and it is fixed. Thanks!

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Development Team

UNAM

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created December 12, 2018 at 11:30 AM
Updated October 8, 2020 at 3:39 PM
Resolved December 19, 2018 at 9:01 PM
TestRail: Cases
TestRail: Runs