Description

This PR adds the following:

Created a bulk import UI option for Moves.
Created a UI interaction space for managing and Viewing Tasks in Development Only
Allows for Multiple Pickups with the same offering, but only one Dropoff still

Something to note is that this is V1, there after a discussion, I'm assuming we will make some changes into a V2.

How Has This Been Tested?

Insomnia Testing of all Paths related to Moves

Screenshots (optional)

Anything Else?

The remaining thing to think about for this ticket is V2
- Multiple Dropoffs — blocked by dynamic min/max expected qty and expectations for those values. Using qty_actual as the upper/lower bracket? We don’t show on the userface what the value we are expecting to be, so how does the user know how much qty to dropoff at one location versus another.
- There are also a lot of tests that don’t expect a proper range for qty_expected_min/max but rather for it to just eq(qty_actual), so going in and setting up “in_between” will be apart of V2
- Source Steps — This is becoming more and more irrelevant except for maybe the validations on which type of step comes before a different one
- Discussions around more validations — How much needs to be dropped off at one location versus another, can we display the expected dropoff amount, insufficient space path (Check if there is another dropoff, check if it has space, otherwise find a spot)
- For validation of inventory, should we be doing futures values or only present?
  - If there are other tasks that will fill the inventory to the point of using it, would we allow for the task to be created?
  - When we have capacity, it would be good to match Warehouse Location Capacity and the moves Bulk Import Screen

Summary by CodeRabbit

New Features
- Warehouse Tasks UI: list, filter, paginate, view details, select/delete tasks; admin menu item visible in development.
- Moves import: new "Moves" import type with CSV validation, per-move resolution UI, import → warehouse task creation, async processing, and receipt/notification options.
- CLI helper to auto-complete move tasks.
Chores
- API endpoints, background worker and rake task to support moves import and task retrieval/deletion.
Tests
- Updated specs for move quantity and step handling.
Style
- Added moves table and status styling.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Note

Introduces Moves bulk import (with pre-processing/resolution and async import) that creates warehouse move tasks, plus a development-only Warehouse Tasks UI and new APIs/jobs to list/view/delete and process tasks.

Imports (Moves):
- Add Import::Move with CSV validation, per-offering resolution data, and processing that creates Warehouse::Task::Move from bulk CSV.
- New endpoints: POST /api/v1/imports/moves_resolutions and POST /api/v1/imports/moves; template download supports moves.
- Frontend: new model ImportMoves, resolutions collection/view, mapping in import UI, and styling for moves tables.
- Background processing: MovesImportJob and rake task jobs:import_moves.
Warehouse Tasks UI (dev-only):
- New router, index/table/show views and templates to list/filter/paginate tasks, view details, navigate, and (dev+admin) bulk-delete.
- Menu entry shown only in development.
Warehouse API:
- Extend warehouse/tasks with show and dev-only destroy; index supports status=incomplete.
- show.json.jbuilder returns task, assignments, and steps.
Warehouse Task logic:
- Warehouse::Task adds incomplete scope.
- Warehouse::Task::Move: creation from bulk CSV, step initialization, auto-complete-on-last-step, emergency handling adjustments, and transfer on completion.
- Step updates: expected qty calculations across pickups, reassignment/skip logic for over/understock, and dropoff qty validation.
CLI/Utilities:
- bin/auto_complete_move.rb to auto-complete a move task.
Tests:
- Update specs for new qty expectations and step behaviors.

^{Written by Cursor Bugbot for commit 216826e. This will update automatically on new commits. Configure here.}

Open Pull Requests

5

2

1