Parts

• 'Wizard' Interface
  • Step 1 - Import parts
  • Step 2 - Associate BOM items
  • Step 3 - Create supplier parts
  • Step 3 - Finalize data
• No data actually saved to database until everything complete
• If no category explicitly set for a row, pre-fill with the current category

• login / logout
• Different actions available based on user account

Each category page displays a list of parts in that category.

Add a table column called 'Stock / Available'

Which shows how many parts are in stock, and how many are available.

Each Part should return the number of parts currently being built for this Part type

Once a build is 'complete' (and outputs moved to the stock location) this should return zero

Each Part should display a total stock aggregate, combining the following numbers:

• Current actual stock
• Current number being built (in progress)
• Current number on order
• Current number allocated to customers
• Current number allocated to builds

Parts shipped out against invoice
Invoice against CustomerOrder

The 'submit' button shouldn't call the callback twice!!! :'(

Shallow copy exists. Needs deep copy which:

• Copies each BOM item
• Copies part image

Prevent user from making a new part which is really the same as an old part

• Look for 'similar named' parts
• Suggest these parts before part creation
• Part of Modal Wizard Form?
  • Step 1 - Create part
  • Step 2 - Check for dupes
  • Step 3 - ???
  • Step 4 - PART!

Date should be DateTime

• When a new part is created in that category, the default location is copied across

If a part can be sold, provide customer pricing information, etc etc

Use this information to pre-fill invoices, etc

e.g. select two parts A / B

Add 10x to A, 20x to B

The items are seemingly updated correctly but both tracking notes get added to each part.

e.g. under A->tracking

• "Added 10 items"
• "Added 20 items"

On part detail page

Each part should return an aggregate of the number of parts currently on order for this part type

e.g. when a part is built or purchased, present a "where does this part go" box, but pre-fill it with the part's default location.

Most parts will only ever live in a single warehouse so this saves a lot of time.

• Pending builds do NOT allocate parts but parts know that some will be used for pending builds
• Allocated builds - parts are selected from stock
• StockItem model needs BUILD field which is where they are marked as allocated
• When a build is marked as 'built' the allocated stockitems are deleted (or marked as 'belongs_to' the output of the build if the parts are tracked

Parts (or 'things' in general?) should have custom tags

Many objects currently have functions which perform inefficient db queries.

e.g.

Part.allocated_build_count

This currently returns a list of allocated builds and then iterates over them, summing the build quantities.

Instead, perform a Sum or Count django annotation query!

There are many such instances where this should be fixed.

• Tasks have sub-tasks (sub tasks all the way down!)
• Assigned to multiple users
• Completion status
• Completion date, etc

Select multiple items and perform bulk actions

Part

• set category
• delete part
• stocktake
• order parts

Stock

• move
• stocktake
• Add and remove stock
• Order stock items
• delete

Hi, everybody.
I am trying to install InveTree on my web server.
I have now installed Python version 3.6.5.
However, because I am a beginner, I am looking for a detailed step-by-step guide to installing Invetree, but I have not been able to find it.
I looked for a manual on how to install it here, but it was just a vague description.
So I need step by step instructions.
For example, can not install InvenTree on a web hosting account?
Can you help me a little bit?
Thank you.

Provide internal URL e.g. link to wiki page with company details

• Tree view of part categories displayed on left-hand side of '/part/' pages
• Displays current category (when appropriate)
• Similar tree for stock locations

A BuildOutput should have an associated batch-code. When the build is complete, all the resulting StockItems get a copy of that batch code

• Edit table 'live'
• Add new row at the bottom of the table automatically
• Where appropriate, filter acceptable choices via AJAX

When shipping or building items, it can be helpful to print out a list of all the items, with a picture, description, quantity.

Then shipping peoples can easily check off each item as they go.

• If I directly run requirments.txt then it installed latest django i.e. In my case it installed 2.1
• But this code base does not support django 2.1 hence either suppert latest django version or add exact supported version in requirements .

e.g.

• Completed Orders

Automate install of postgresql database

• User must log in
• Groups
• Different views are available for given user group

• Consistent style between all such pages
• Templated?

hover-over image to reveal 'edit' ?

• Excel / CSV
• Pretty printing to PDF

e.g. during builds a certain quantity of parts may be wasted or lost.

Provide a clean way to keep track of this and enter the data back in (e.g. at the end of the build process)?

Not just direct children, display all sub-levels

Inspect the db to get the number of parts allocated (for this part type);

• Allocated to builds
• Allocated to customer orders
• Allocated for any other purpose??

• Stocktake
• Move

Both these forms report a server error: e.g.

MoveStockItemForm has no field named 'serial'

For some reason the serial number is required to be submitted...

When trying to create an stock item, the quantity can not be set as it is marked read only. I may be missing something, but shouldn't that field be able to be set when creating the item since it cannot be set to NULL?

I changed it to so it could be set as a workaround for now. Let me know if I'm overlooking something.

If a part category is deleted, all child parts should move to the parent category.

If the category was top-level then the parts are "orphaned" as top-level parts. They can later be moved.

please advice.

Parts can add other parts as "BOM items".

It is necessary to add extra logic to prevent a part from being added as a "BOM item" of one of its own BOM items

/part/

• Live filtering by name, category, IPN, etc
• Live column ordering

• "Company" is sufficient
• Add 'is_supplier' and 'is_customer' fields
• Company can be a supplier OR a customer OR both!
• e.g. need to be able to make a purchase from a company and also make a sale to it

• csv / excel / etc
• For each import, also provide downloadable 'template' which can be filled in
• "Guess" at fields if there is a discrepancy

On parts pages, only display part category tree.

Don't display "sub-category" list - only the tree!

Display tree-icon to the left of the breadcrumb view. Pressing this toggles the tree view on the left-hand side.

Pass the current 'category' to the tree view code to ensure that the current category is visible when the tree is expanded.

Save tree display state to session.

When creating a new purchase order, set the default value to the "next highest" order

(whatever that is?)

• Maybe have the ability to set a prefix for different types of orders
• PO
• CSO
• INVOICE

A CustomerOrder may be partially fulfilled in a given shipment.