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

CRUD Request Cancellation Reasons

    XMLWordPrintable

    Details

    • Template:

      Description

      Cancel reasons

      Purpose: To implement settings to create, read, update and delete the Cancel Reasons that a staff person will choose from when cancelling a request. These reasons may be manually assigned and/or automated.

      As a library administrator, I want to be able to create, read, update and delete cancellation reasons that I can document why a request was cancelled. I also need to be able to reorder the reasons that have been created, so that, during request cancellation, the reasons appear in the Cancel Reasons drop down menu in the order that best suits my institution.

      Scenarios:

      1. Scenario
        • Given the Request Cancellation Reasons page under Settings > Circulation -> Request cancellation reasons
        • When displayed
        • Then a Request cancellation reasons control should display under the header "Request cancellation reasons"
      2. Scenario
        • Given the New Request cancellation reasons control
        • When a new Request cancellation reason is created
        • Then Cancel reason, Description (internal), and Description (public) can be specified
          (Note: Cancel reason is required but Description (internal) and Description (public) are not)
      3. Scenario
        • Given the Request cancellation reasons control
        • When a new Request cancellation reason is created
        • Then it should display in the list of created Request cancellation reasons on the Request cancellation page in Settings
      4. Scenario
        • Given the Request cancellation reasons control
        • When a new Request cancellation reason is deleted
        • Then it should be removed from the list of created Request cancellation reasons on the Request cancellation page in Settings
          (Note: all cancellation reasons should be deletable except Other, which should never be deletable)
      5. Scenario
        • Given the Save button on an existing Request cancellation reason in edit mode
        • When clicked
        • Then the Request cancellation reason should be updated per what is entered by the user
          (Note: Cancel reason is required but Description (internal) and Description (public) are not)

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                md331 Mark Deutsch
                Reporter:
                taniafersenheim Tania Fersenheim
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases