admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-07-15 19:41:19 +00:00
parent 4a38315e8b
commit 65f93ba621
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
ayanova/devdocs/todo.txt
View File

@@ -424,16 +424,14 @@ todo: many biz objects are not using new PUT methodology
CURRENTLY DOING:
todo: Status on work order doesn't seem to be preventing "Who can select" by role properly
Make it not present status that are not supposed to be available
put a back end rule in validation to prevent it as well
Also, the seeded data roles are really fucked up and include some dubious roles and needs to also have some for tech - restricted specfically
todo: Status on work order seeded data roles are really fucked up and include some dubious roles and needs to also have some for tech - restricted specfically
i.e. they need to be logically correct as to what roles can select
todo: expose Roles as optional column for report templates list
todo: expose Roles as optional column for work order status list
todo: units on work order are not limited to customer on work order??
TODO 1: Test address / units select alternate when have units working