openboxes / openboxes/openboxes

Update the inventory management screen

Open
#1,035 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stakeholder: community status: needs discussion type: feature
Dominant language
Groovy
Stars
899
Forks
503
Avg merge
3d 7h
Merged PRs (30d)
54

Description

Using 0.8.6

Actual behavior:

The inventory management screen is extremely limited in its functionality, only supporting tags.

Expected behavior:

The inventory management screen should be a list of products with their previous quantity, and a field for their current quantity and a "reason" dropdown. The dropdown should unlock if the user enters a value for the current quantity that doesn't match the previous quantity, and would have reasonable reasons as to why that might be the case (eg expired, damaged, lost etc, similar to receive shipment interface).

By default, the list of products should include everything enabled for this particular location. Filtering of that list by keyword search, by bin, by product, by tag, and/or by stocklist should be supported. Selecting each option should restrict the list further (AND) rather than including products that meet any of those filter requirements (OR).

When all of the product quantity changes are recorded, saving the changes should create transfers for each product just like the Record Stock option on the stock card.

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 inventory management screen and compare its current tag-only behavior with the Record Stock option on the stock card. Done means the screen lists enabled products, supports the specified AND filters, records quantity-change reasons, and creates transfers when saved.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.