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-10-07 00:10:33 +00:00
parent 47831f9be1
commit d106e9d44a
2 changed files with 13 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
ayanova/devdocs/todo.txt
View File

@@ -19,31 +19,23 @@
SVC-SCHEDULE OUTSTANDING ITEMS SVC-SCHEDULE OUTSTANDING ITEMS
See about including no tech items as sched should show them as unassigned or something it's built in for non matches but I could enable that anyway
it was in v7
maybe always far right by default, but then people may not want it to take up space
ensure if there are no unassigned that it doesn't show at all, i.e. it would come back with categories from schedule controller svc route if there are any
maybe included with the tag selector as a checkbox to automatically include unassigned
maybe it's a drill into unassigned on it's own?? but then can't drag to a tech as would be useful feature of this
3698 - hide unassigned tech slot (or case 3697 above would take care of that too)
need ability to drag to another tech in category view need ability to drag to another tech in category view
Drill down to schedule by user so can click through user to schedule for *that* user alone, (brings up home-schedule maybe or I guess a copy would be easiest) bugbug: mouse move day view is firing twice for in category view needs filter
this will solve issue when people say "Why can't I view month but for one user instead?"
probably easiest from both the User edit form for admin and from the svc-schedule form (maybe a link on their names at top?? Opens same view currently selected but for that *one* user)
This is an important and must have feature for inital release
docs notes docs notes
unassigned slot and how it works unassigned slot and how it works
visible if there are any that day in team view otherwise doesn't show
team view vs day view team view vs day view
how to use the controls etc how to use the controls etc
small screen view vs larger small screen view vs larger
Drill down to schedule by user so can click through user to schedule for *that* user alone, (brings up home-schedule maybe or I guess a copy would be easiest)
this will solve issue when people say "Why can't I view month but for one user instead?"
probably easiest from both the User edit form for admin and from the svc-schedule form (maybe a link on their names at top?? Opens same view currently selected but for that *one* user)
This is an important and must have feature for inital release
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) 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)
"show all " but on a schedule to view that way instead of a data table "show all " but on a schedule to view that way instead of a data table

7
ayanova/src/views/svc-schedule.vue
View File

@@ -640,6 +640,12 @@ export default {
return elapsed < 200; return elapsed < 200;
}, },
mouseMoveDayView(tms) { mouseMoveDayView(tms) {
//Vuetify bug in calendar apparently where it fires for both day and day-category views
//since I set them to both call into this same method I need to ignore the incorrect one
if (!tms.category && this.viewType == "category") {
return;
}
console.log("mousing", tms.category);
//no event being dragged or exgtended? //no event being dragged or exgtended?
if (!this.dragEvent && !this.extendEvent) { if (!this.dragEvent && !this.extendEvent) {
return; return;
@@ -647,6 +653,7 @@ export default {
const mouse = this.toTime(tms); const mouse = this.toTime(tms);
if (this.dragEvent && this.dragTime !== null) { if (this.dragEvent && this.dragTime !== null) {
console.log("dragging, category:", tms.category);
//# DRAGGING PATH //# DRAGGING PATH
const start = this.dragEvent.start; const start = this.dragEvent.start;
const end = this.dragEvent.end; const end = this.dragEvent.end;