Uploaded image for project: 'ui-requests'
  1. ui-requests
  2. UIREQ-206

Null Hold Shelf Expiration Results in Ugly Error

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Core: F - Sprint 57
    • Story Points:
      3
    • Development Team:
      Prokopovych

      Description

      Steps to repro:

      1. Log into folio-testing or folio-snapshot
      2. Go to Requests
      3. Find a request that is Open - Awaiting pickup or, if there aren't any, find one that is Open - Not yet filled and check the item in (this will change the request status)
      4. Edit the request that is Open - Awaiting pickup
      5. Clear out the hold shelf expiration date
      6. Save

      Expected: Should save without generating an error

      Actual: Backend error displays

      NOTE: We might want to tackle the related linked bugs below at the same time as this one.

        TestRail: Results

          Attachments

            Issue Links

            defines

            New Feature - New feature requests UXPROD-1374 Get Hold Shelf Expiry Period from Service Point

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. UIREQ-192 Requests: Request Expiration Date Not Displaying on View and Throwing Error When Deleted

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIREQ-207 Dates Shown on Edit Page After Save Are 1 Day Prior to Dates Selected

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-194 Requests: Populate the Hold Shelf Expiration Date when a request becomes "Open - Awaiting pickup"

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

              Activity

                People

                Assignee:
                mpk35 Michal Kuklis
                Reporter:
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases