ayanova/devdocs/todo.txt

@@ -46,7 +46,12 @@ CURRENT TODOs
 =-=-=-=-=-=-=
 
 
-TODO: MOVE THIS DOWN?  AFTER ALL WIDGET FORM STUFF IS DONE Form customize UI
+TODO: WIDGET EDIT FORM SAVE AND NEW BUTTON LIKE V7?
+	- will the menu be too crowded? 
+	- How often really will this be needed?
+
+TODO: FORM CUSTOMIZATION FORM
+	- Do before main grid stuff below
 	- Where you create custom fields and edit 
 	- Set if visible / hidden
 		- Ties into main grid stuff below
@@ -59,7 +64,7 @@ TODO: MOVE THIS DOWN?  AFTER ALL WIDGET FORM STUFF IS DONE Form customize UI
 				- This way the client is always working with the correct data and also no mass changes are made at the server and if the user chooses not to save the record at the client then nothing is affected
 				- Maybe a function that all customfield able objects call?
 
-TODO: Grid form analysis and completion
+TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION
 	- Main grid time is off from edit form time by -1 hour
 	- Should users be able to set columns or am I really going to force it to a preset?
 			- I had a customer today request the Description field from unit show in the workorder service grid, it doesn't do that
@@ -88,8 +93,9 @@ TODO: Trial route ui support in client
 	- Would be useful to see and manage OPS things related to deployment to server just to save time, can refine them later
 
 
-TODO (NEEDS re-test ON MOBILE for appearance and functionality): Reports - stub out
+TODO: REPORT LIST STUB
 	- Stub out some fake reports in a drop down selection for testing, doesn't have to do anything but be present
+	- Test on mobile once done
 	- WAS implementing as a dialog, that needs to be replaced now, either I need to follow the vuetify dialog example and put it in the shell app.vue or I'm going to use the dialog library I already have once I get an answer on templates
 		- If I use the vuetify example it means there needs to be a dialog in the shell that is activated from any form inside it but it also needs to be bound and shit and won't be very clean
 		- If I use the library dialog component and figure it out in theory it will just popup when required and not pollute the shell template with anything.  I guess it inserts itself into the dom.
@@ -112,11 +118,12 @@ TODO: SERVER STATUS
 TODO: Why is there an error in the console when a user is not logged in and opens client?
 	- It should just go to login, no error should show in the console
 
-
-TODO: DataDump plugin needs an explanation of what it is in the flow, right now it's completely cryptic and people may be using it for stuff thinking it's for something it's not
+TODO: ANY TIME - SIDE v7 STUFF DataDump plugin needs an explanation of what it is in the flow, right now it's completely cryptic and people may be using it for stuff thinking it's for something it's not
 	- Also, verify it's manager account only that can run it or maybe someone with total rights to everything?
 
 TODO: Record history display / check other AyaNova 7 options / buttons that need to carry forward
+	- Check what is in v7 that I missed on edit forms, make TODOs for them here
+	- Check what is in RAVEN STAGE 1 cases on RockFish and make TODOs for them here
 	- implement and componentize
 	- Record history could be displayed on a timeline: https://vuetifyjs.com/en/components/timelines
 	- Make sure it's scrollable maybe and doesn't take up too much space 
@@ -124,7 +131,7 @@ TODO: Record history display / check other AyaNova 7 options / buttons that need
 	- Probably going to need a server route but let the UI drive it (timeline view requirements maybe?)
 	- Record history "slot" maybe just like the VUE Way so that it can be easily optionally shown or not in it's slot
 
-TODO: - Time zone mismatch message sb localized and far shorter
+TODO: - Time zone mismatch message sb localized and far shorter with an actionable link to that area of the client
 	
 TODO: WIKI
 	- componentize
@@ -133,8 +140,7 @@ TODO: WIKI
 TODO: Attached documents
 	- componentize
 
-TODO: save and new button in edit form like v7? Or only from main?
-	- will the menu be too crowded?
+
 
 RETEST HERE ON ALL DEVICES
 
@@ -144,6 +150,15 @@ TODO: Clean up TODO list, have only actionable, not completed items.
 	- Make a to_test.txt doc so can move todo's to to test doc for testing
 	- anything in this doc that isn't related directly to individual todo's other than a small big picture stuff at top sb elsewhere
 	- Idea is to have a focused, clean actionable list here.
+	- Prioritize any basic stuff that will be replicated over and over again
+		- i.e. regular edit forms, not schedule or workorder form which will require their own separate work and are not replicated 
+		- want to get going with all the background object types like clients and users etc before I try to make the schedule and workorder forms
+	- Identify any unique time consuming items and put them in their own block of todo's 
+		- Self serve server stuff
+		- workorder form
+		- Accounting integration and other plugins
+		- import datadump etc		
+	- There is a lot of crap at the bottom of this document in this todo!
 
 TODO: NOW THAT FORM IS THERE MOSTLY, CLEAN UP CODE FOR RE-USE in many other forms
 	- Look for things to componentize
@@ -238,14 +253,6 @@ FIXES REQUIRED
 - Don't like popup messages, would rather see a notification icon and be part of that unless it's super critical
 	- Implement a toaster or some similar notification 
 
-Figure out why custom fields don't exist in widgets test data and put it there so can code it.
-Put all the widget fields on the form
-Check rights when navigating to the form
-Fetch the record when the form opens
-Localize the validations
-Ensure my own validations work to match the biz rules for the widget form.
-Add update and save code
-Make all fields work according to specs below
 
 
 	Make a basic crud form with all the fields necessary, then iterate over it adding the items below.