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
2022-02-27 21:18:34 +00:00
parent 1d049bdea6
commit 91d79ab063
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
ayanova/devdocs/todo.txt
View File

@@ -22,6 +22,13 @@ FIRST CLIENT SOURCE CODE COMMIT JAN 3rd 2019
# OUTSTANDING MAJOR AREAS TO BETA # OUTSTANDING MAJOR AREAS TO BETA
# NOW DOING: - triaging list of must have widgets, cleaning up layout to squeeze them in (maybe done), then finishing up the must haves
make sure nice to haves or not done get cased somewhere for future v.next or whatever
figuring out the seed data adn will it suffice for widgets required once have figured out widgets required
(demand drives features not features awaiting demand)
# SEEDING ISSUES
seeder wolabor is being created in the future fucking the kpi stuff or at least looking weird seeder wolabor is being created in the future fucking the kpi stuff or at least looking weird
no labor or date centric items should be created in the future, that's nonsensical no labor or date centric items should be created in the future, that's nonsensical
@@ -34,10 +41,9 @@ seeder wo need new fields and generate data to show off and test kpi widgets and
Also, can we calc "time to respond" based on anything extant or should there be some kind of additional field / system for that Also, can we calc "time to respond" based on anything extant or should there be some kind of additional field / system for that
i.e. maybe a workorder status is also a response status like some are closed??, then a mirror first response field like completeddate i.e. maybe a workorder status is also a response status like some are closed??, then a mirror first response field like completeddate
dashboard widgets
should support multiple copies if an item is configurable # WIDGET ISSUES
- Widgets to make for beta in order of priority - Widgets to make for beta in order of priority
**MUST HAVE*** **MUST HAVE***