Built as the default: closed sets (hold: Waiting on material, Waiting on purchasing / PO, Question for engineering or clerical, Drawing / BOM problem, Other with a note; short: Not in stock, On order, Back-ordered, Damaged / rejected, Wrong part received, Needs cutting / prep, Other).
To answer: keep, add reasons, or allow free text.
Plan reference: Q20 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
**Built as the default:** closed sets (hold: Waiting on material, Waiting on purchasing / PO, Question for engineering or clerical, Drawing / BOM problem, Other with a note; short: Not in stock, On order, Back-ordered, Damaged / rejected, Wrong part received, Needs cutting / prep, Other).
**To answer:** keep, add reasons, or allow free text.
---
Plan reference: Q20 in [docs/PLAN.md](https://gt.pescoinc.biz/spencerm/PacketStation/src/branch/main/docs/PLAN.md) (open questions). Answer here; the build takes the default until then.
More detail, since you asked. These do not come from VISUAL.
A hold is when someone stops a packet (for example the warehouse or the shop cannot go on). A short is when the warehouse cannot pull a BOM line. In both cases the person picks a reason in Packet Station from a fixed list:
Hold: Waiting on material, Waiting on purchasing / PO, Question for engineering or clerical, Drawing / BOM problem, Other (needs a note).
Short: Not in stock, On order, Back-ordered, Damaged / rejected, Wrong part received, Needs cutting / prep, Other.
A fixed list lets the boards and reports group by reason. The old build took any typed text.
The question: keep these lists, add reasons (which?), or allow free text?
More detail, since you asked. These do not come from VISUAL.
A hold is when someone stops a packet (for example the warehouse or the shop cannot go on). A short is when the warehouse cannot pull a BOM line. In both cases the person picks a reason in Packet Station from a fixed list:
- Hold: Waiting on material, Waiting on purchasing / PO, Question for engineering or clerical, Drawing / BOM problem, Other (needs a note).
- Short: Not in stock, On order, Back-ordered, Damaged / rejected, Wrong part received, Needs cutting / prep, Other.
A fixed list lets the boards and reports group by reason. The old build took any typed text.
The question: keep these lists, add reasons (which?), or allow free text?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Built as the default: closed sets (hold: Waiting on material, Waiting on purchasing / PO, Question for engineering or clerical, Drawing / BOM problem, Other with a note; short: Not in stock, On order, Back-ordered, Damaged / rejected, Wrong part received, Needs cutting / prep, Other).
To answer: keep, add reasons, or allow free text.
Plan reference: Q20 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
Please provide more information. Do these notes come from visual?
More detail, since you asked. These do not come from VISUAL.
A hold is when someone stops a packet (for example the warehouse or the shop cannot go on). A short is when the warehouse cannot pull a BOM line. In both cases the person picks a reason in Packet Station from a fixed list:
A fixed list lets the boards and reports group by reason. The old build took any typed text.
The question: keep these lists, add reasons (which?), or allow free text?
yes keep these lists
Noted: the hold and short reason lists stay as they are. Recorded in docs/PLAN.md (PR 53). Closing.