rubyforgood / rubyforgood/human-essentials

Inventory Coming In / Going out -- Rework to Inventory Flow, including date range.

Open
#5,249 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Difficulty—Intermediate stale
Dominant language
Ruby
Stars
593
Forks
593
Avg merge
4d 22h
Merged PRs (30d)
41

Description

Summary

Rework the inventory in / inventory out tabs into an inventory flow tab. Add a date range.

Why

Increase usefulness of the information

Details

See the mockup of the desired screen, below.

Quantity in has donations, purchases, adjustments that increase the inventory.
Quantity out has distributions and adjustments that decrease the inventory

Kit allocations result in quantity in for the kit, and quantity out for the components

See the current Inventory In and Inventory Out tabs for details

Change is Quantity In minus Quantity Out. Negatives are presented in red.

If need be, change this to work off the eventables rather than itemizables. (The author is not sure which it does.)

Audits are ignored.

Please also add "(based on entry date)" to the Date Range label.

Image

Remove the current Inventory In and Inventory Out functionality

Criteria for completion

  • behaviour as described

  • automated tests to confirm behaviour

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the current Inventory In and Inventory Out tabs, the attached mockup, and the existing eventables/itemizables implementation to determine how inventory entries are sourced. Done means a date-range Inventory Flow tab shows the specified quantities and change, ignores audits, marks negatives in red, updates the label, removes the old functionality, and has automated tests confirming the behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
data, full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.