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
2020-12-17 01:20:06 +00:00
parent 980f188d89
commit 74887975b7
1 changed files with 6 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
ayanova/devdocs/todo.txt
View File

@@ -44,20 +44,18 @@ TODO: //MIGRATE_OUTSTANDING comment tag
currently doing: currently doing: Reminder - was regular non followup schedulemarker, Review - was follow up schedule marker
Check for alternative names for review
continue case 3511 and reading spec doc to ensure got the gist of it there continue case 3511 and reading spec doc to ensure got the gist of it there
Still determining where and what to expose in the UI Still determining where and what to expose in the UI
considering a Review area in every area of the UI so one in Accounting, Customers, inventory, service considering a Review area in every area of the UI so one in Accounting, Customers, inventory, service
each area shows only items related to that area so that manager can see everyone's Reviews for that area of work each area shows only items related to that area so that manager can see everyone's Reviews for that area of work
as a full role for that area can assign to whoever and view for whoever, whereas limited roles see their own only. as a full role for that area can assign to whoever and view for whoever, whereas limited roles see their own only.
One fleshed out the case do the same for 3425 for Reminders and look into spec docs just in case
Reminder - was regular non followup schedulemarker
Review - was follow up schedule marker
fuck, review and reminder are too much alike, reminder I like but review while accurate sounds off
maybe I should go back to follow up or something similar, check thesaurus / translator before going too far into this
find an easily translated word in thesaurus that is clear in all languages
Need to code for both at back end, pay attention to changes in field names in cases Need to code for both at back end, pay attention to changes in field names in cases
Front end may be a bit more time consuming on this one so do the v8 migrate maybe first so have realistic data to work with Front end may be a bit more time consuming on this one so do the v8 migrate maybe first so have realistic data to work with