maebeale
maebeale
- Each `AbuseType` has "`CoreBoxItems`", or, `InventoryTypes` that should be added to `Boxes` by default (once we create a Box) - We want to have a CoreBoxItem builder that is...
User will need to see: - total items grouped by `inventory_type` in stock across all locations, with some kind of color indicator for when quantity is below 5 - `inventory_type`...
- disable the button after click - if the form errors -- reengage the button so they can make their fixes and resubmit
To walk to the "next" lifecycle phase upon completion of the existing one, there should be dynamic buttons at the bottom of each of those pages (that depend on permissions...
@sarslanoglu should this be `@box_requests = @box_requests.where...` ? _Originally posted by @maebeale in https://github.com/rubyforgood/voices-of-consent/pull/414_
Add edit buttons (with pencil icon) to left of user emails on Users index that to to that User's rails edit page. This page should only be viewable to people...
Depends on #310 Using the factories, we'd like to create seeds to create ~30-50 box_requests (and boxes) with the to represent all parts of the box_request/box lifecycle. Here's a SO...
- Admins need to be able to create and edit Users - Back end already exists -- just need the views - `/user_management` should have more than just invited/accepted status...
We have need for varied `user`, `box_request`, `box`, and `box_item` factory traits (We have existing factories) for use in tests, and later to create seed data. If we had `box`...