This commit is contained in:
@@ -218,6 +218,8 @@ todo: cypress testing for load testing etc
|
||||
|
||||
## SERVER MISC ITEMS
|
||||
|
||||
todo: seeder is putting customer users in as techs in sample workorders (on scheduled user for sure at least)
|
||||
|
||||
todo: notify on server boot?? (general notify to admin user or whatever?)
|
||||
or on shutdown?
|
||||
|
||||
@@ -384,6 +386,17 @@ todo: many biz objects are not using new PUT methodology
|
||||
|
||||
CURRENTLY DOING:
|
||||
|
||||
MISC WO ITEMS that came up
|
||||
scheduled user conflict is triggering error properly on initial create and save but NOT when edited and saved
|
||||
possible fuckiness with errors on update rather than initial save (hidden extra ID column?)
|
||||
it *is* showing on woitem part that there is an error and it is showing in top for error alert box
|
||||
but not showing for exact field or row in grid
|
||||
This is likely occurring with other things, may not have tested this scenario of update and error properly
|
||||
so replicate the fix whatever it is or look for the same issue
|
||||
|
||||
Scheduled user selecting rate on new isn't populating rate-viz, (server is on save though)
|
||||
|
||||
|
||||
3720 3: BUMPABLE CASE I THINK prevent double booking a tech (some kind of warning)
|
||||
availability feature??? maybe bump as a new availablity feature where user picks from a popup schedule for that tech?
|
||||
if not maybe a alert from the workorder itself when they save saying double booked??
|
||||
|
||||
Reference in New Issue
Block a user