ayanova/devdocs/todo.txt

@@ -12,6 +12,10 @@ todo: when have po, can po serial number be set by user and accepted by postgres
 	I think it can with the definition I have set up.
 	this would be useful for scenarios like 4alarm with the oddball po and other auto generated id numbers
 
+todo: it's a bit hard to click on a single digit or character link in a data table
+	e.g. serial number 1 of a po
+	can the region be expanded with invisible text or something?
+
 todo: "Picklist display formats" translation used in admin settings
 	rename to something more generic like selectable items display format or something as it's used in displaying in lists as well like part assembly parts
 
@@ -23,6 +27,11 @@ todo: WHEN HAVE WORKORDER FORM customer popup notes need to pop pop pop, forgot
 	However, I also find that incredibly annoying but I guess that's the point :)
 
 ## SERVER MISC ITEMS
+
+todo: GetWorkorderSerial/name from leaf nodes 
+	traverse up the tree and fetch the serial number
+	once coded fixup in purchaseorderbiz::getasync MIGRATE_OUTSTANDING bit
+
 todo: actual customer reports so can figure out datalist for bringing other names in
 	I'm thinking an alternate mode for reporting where there are more defined links in the list to fetch names?
 
@@ -97,6 +106,10 @@ todo: how to add locale keys in future after release without erasing all data?
 
 CURRENTLY DOING: PurchaseOrder 
 
+Question: part number and part name, why both, it's fucking up the UI?
+	Can we settle on one only, it's confusing and weird
+	Yes, NUMBER is the only required in v7 sb required in v8 as well
+	name is for picklists not grid lists inside po form
 
 PO UI for items:
 	Use ops-backup form list of backups as concept, it uses a v-data-table