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

Requests - capture action information during edit

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Duplicate
    • None
    • None

    Description

      Purpose: To capture and display edit actions on a request. Request actions track the history of what has happened to a given request. All requests will have at least one request action (the creation of the request) and as things happen to the request (it is edited, it is cancelled) new actions will be logged against the request.

      This story will focus on capturing the request action associated with editing the request.

      Scenarios

      1. Scenario
        • Given a the “Update Request” button on the Edit request screen
        • When clicked
        • Then the following information should be captured for later display:
          • Date and time the edit was performed
          • The nature of the action (see note)
          • The username of the user that edited the request (this could be either a staff person or the requester)

      NOTE: These edit actions should be recorded:

      • Request expiration date changed
      • Hold shelf expiration date changed
      • Fulfillment preference changed
      • Pickup location changed
      • Delivery address changed

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                taniafersenheim Tania Fersenheim
                taniafersenheim Tania Fersenheim
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases