Uploaded image for project: 'mod-orders'
  1. mod-orders
  2. MODORDERS-125

Spike: Create endpoint that is an entry point to the Receiving flow

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.0.0
    • Labels:
      None
    • Template:
    • Sprint:
      ACQ Sprint 55
    • Story Points:
      1
    • Development Team:
      Thunderjet

      Description

      Purpose: Implement endpoint that provides the information to start the Receiving flow. This information includes at least:

      • total number of pieces
      • number of expected pieces
      • Id's of the expected pieces so that UI can indicate which piece exactly we are about to receive

      High-Level Requirements:

      • create a new schema in acq-models for the entry endpoint response that defines required information
      • Implement GET /orders/order-lines/<id>/pieces endpoint that returns information to start the Receiving flow

      The flow would be something like this:

      1. open the orders app, search/filter - a list of orders appears (GET /orders)
      2. select an order - order details appears (GET /orders/<id>)
      3. select the "receive" button in the details pane - the receiving modal comes up and displays receiving info
        • for each po_line.... (GET /orders/order-lines/<id>/pieces) - based on mocks we want to see expected & received.
      4. details are entered, e.g. number of each po_line to receive, notes, etc.
      5. form is submitted - "Update Item Details" modal is displayed
      6. item details are entered, e.g. barcode, location, status, etc.
      7. form is submitted (POST /orders/<id>/receive)
      8. Receiving History is displayed (GET /orders/receiving_history -> purchase_order_id == <order id>)

      Acceptance Criteria:

      • the schema for a new endpoint is created
      • new entry endpoint is implemented
      • unit tests are updated
      • api tests are updated

      Spike Acceptance Criteria

      • All open questions have been answered
      • follow-on user stories have been created to track the implementation
        • appropriate links have been added to these stories (back to here, and possibly to other stories)

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                cmcnally Craig McNally
                Reporter:
                pavelk-epam Pavel Korolenok
                Tester Assignee:
                Craig McNally Craig McNally
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases