This commit is contained in:
@@ -10,7 +10,50 @@
|
|||||||
## ROUGH SCHEDULE
|
## ROUGH SCHEDULE
|
||||||
|
|
||||||
|
|
||||||
Schedule form
|
# Schedule form
|
||||||
|
based on datalist with lots of filter "handles" on it
|
||||||
|
needs a way to select which techs to show in which order, I guess ideally an additional saved view part as with filter for datalist
|
||||||
|
maybe could just add a small key to the datalistfilter that is only applicable to this?
|
||||||
|
Ideally the same datalist for all purposes so can just filter accordingly with built in pre-filter if single user etc
|
||||||
|
This is also so datalist can drive reporting
|
||||||
|
Needs to consolidate all sources of info that can go on display
|
||||||
|
sourcetype of event so wo, review, reminder...
|
||||||
|
Keep in mind calendar / schedule based widgets which could be a view and a format saved (no UI space to adjust)
|
||||||
|
so maybe a "Make this view a dashboard widget" option?
|
||||||
|
Also, schedule based widgets give us something to immediately provide with initial release if we haven't got to all the widget types yet
|
||||||
|
From omnibus case 729
|
||||||
|
- user able to set whether they want to see 15 or 30 or 1 hour increments
|
||||||
|
- user able to set start time for day (i.e. some want 7am, some want 6am, some want 10 etc)
|
||||||
|
- ability to set to display either a single day (today) or a week around todays date, etc.
|
||||||
|
- case 1219 now incorporates saving user settings for days viewed on exit - so that part is already done (DON"T FORGET TO SAVE CONFIG USER HAS SET)
|
||||||
|
- Personal schedule in home area shows review, reminder and wo scheduled items for techs
|
||||||
|
only shows personal to that user
|
||||||
|
- Shared schedule for dispatch service mgmt area shows all techs and wo items
|
||||||
|
filterable to which techs to include
|
||||||
|
savable filter
|
||||||
|
savable orderable which techs in which order
|
||||||
|
savable all settings
|
||||||
|
should act like filters for datalists but also for configuration stuff
|
||||||
|
user selects filter, techs to show, what order etc and then it just uses that when they select it as a view
|
||||||
|
Views could also drive schedule type dashboard widgets as well
|
||||||
|
Copy the fuck out of google calendar UI layout, it's popular and easy to use https://calendar.google.com/calendar/u/0/r/week?pli=1
|
||||||
|
|
||||||
|
|
||||||
|
CASES
|
||||||
|
3766 - view schedule filtered by customer so can see at a glance all past and future for a single customer (more data table filter similarity)
|
||||||
|
3697 - arbitrarily order schedule by user instead of built in by lastname
|
||||||
|
3698 - hide unassigned tech slot (or case 3697 above would take care of that too)
|
||||||
|
3511 - "Review" feature (was followup sched marker), appointments that link to objects and display alternatively in UI
|
||||||
|
3425 - "Reminder" feature (was non follow sched marker)
|
||||||
|
1686 - ability to set how much stuff displays / alt schedule / calendar view??? Not sure really, it's a mish mash
|
||||||
|
729 - mass misc omnibus copied to above the useful bits
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Dashboard / widgets
|
Dashboard / widgets
|
||||||
Installer INNO
|
Installer INNO
|
||||||
version with postgres included, version without postgres included
|
version with postgres included, version without postgres included
|
||||||
|
|||||||
Reference in New Issue
Block a user