This commit is contained in:
@@ -467,9 +467,7 @@ CASES TODO:
|
|||||||
Some initial workorder cases to do
|
Some initial workorder cases to do
|
||||||
|
|
||||||
1908 1: set new durationtocompleted field on wo header upon setting to a closed status, also show it in the main data list
|
1908 1: set new durationtocompleted field on wo header upon setting to a closed status, also show it in the main data list
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3500 1: implemented but needs the docs and seed data to illustrate the feature
|
3500 1: implemented but needs the docs and seed data to illustrate the feature
|
||||||
make a shadow units customer in seeder sample data
|
make a shadow units customer in seeder sample data
|
||||||
make units under shadow units customer
|
make units under shadow units customer
|
||||||
@@ -485,22 +483,20 @@ CASES TODO:
|
|||||||
3769 2: if public FromQuoteId, FromPMId or FromCSRId are set on wo header then it should surface a button or menu option to open the related object(s)
|
3769 2: if public FromQuoteId, FromPMId or FromCSRId are set on wo header then it should surface a button or menu option to open the related object(s)
|
||||||
I think a menu option would be cleanest as you wouldn't always want to see it in your face but have it available
|
I think a menu option would be cleanest as you wouldn't always want to see it in your face but have it available
|
||||||
3843 1: prevent negative amounts on woitempart.quantity (rule I guess)
|
3843 1: prevent negative amounts on woitempart.quantity (rule I guess)
|
||||||
3868 2: be able to select any unit on wo, needs to be implemented at the UI as it should default to only this customers units (but not reject if customer changed)
|
|
||||||
and also test this out to see if it works properly
|
|
||||||
maybe select by tag is enough to fulfil this case?
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
AFTER ABOVE ITEMS AND HAVE SUBSTANTIALLY COMPLETED WO
|
AFTER ABOVE ITEMS AND HAVE SUBSTANTIALLY COMPLETED WO
|
||||||
|
|
||||||
todo: IMPORT workorders FROM V7 needs to be coded once the cases are completed
|
todo: IMPORT workorders FROM V7 needs to be coded once the cases are completed so it can be tested thoroughly and ongoing
|
||||||
note that v7 wostatus needs to be dual imported into both new wostate and new woitemstatus separately
|
note that v7 wostatus needs to be dual imported into both new wostate and new woitemstatus separately
|
||||||
Joyce suggested making it optional to have the import-v7 tag
|
Joyce suggested making it optional to have the import-v7 tag
|
||||||
think it over and the pros and cons of having it, maybe some notes are there on it
|
think it over and the pros and cons of having it, maybe some notes are there on it
|
||||||
I might have been thinking it's a quick way to mass delete any old stuff no longer wanted in the new version for users
|
I might have been thinking it's a quick way to mass delete any old stuff no longer wanted in the new version for users
|
||||||
or maybe to know an item was imported in case of support maybe or issue?
|
or maybe to know an item was imported in case of support maybe or issue?
|
||||||
|
|
||||||
|
todo: circle back to big list of discovred misc items above and fix them (arghh, but nice to have been completed)
|
||||||
|
|
||||||
TODO: Need stress test for client that can generate workorders in parallel for load testing
|
TODO: Need stress test for client that can generate workorders in parallel for load testing
|
||||||
------------------------------------------
|
------------------------------------------
|
||||||
|
|||||||
Reference in New Issue
Block a user