Closed willn closed 8 months ago
This is still a great idea, however it will take some effort. Currently, the preferences that are displayed only show what was written to the database. There is a Worker->addNonResponsePrefs() method which only modifies the number of shifts that need to be filled... aka for the auto-assignment routine, not for the reporting side.
I still believe this would be a really helpful feature.
This would save a lot of time, particularly if we can mark these folks as being capable of being used anywhere.
It appears that the raw list of data is generated by a SQL request in Calendar::getWorkerDates(). This data is returned effectively as the raw results.
There is a Roster::addNonResponderPrefs(), which calls Worker::addNonResponsePrefs(), and loads that into the established data structures.
These would need to be weaved together in order for them to make sense.
Currently when someone doesn't fill in their survey, they get something between avoid and OK, like a .5 score or something. These names ought to be displayed in the calendar dates in the summary report to make finding trades easier... in fact, their names should probably be highlighted as being a "pinch hitter", someone who can be moved anywhere that's needed.