Small task tracking

[ormiret]

Thinking to make something to track small tasks that can be picked up by any volunteer.

Things like emptying bins, (un)plugging cables in DKs, moving stuff from A->B.

Might also be useful for task tracking during setup/teardown?

Task info

• Title
• Description
• Location
• number of people needed
• Deadline optional - could be just ASAP
• Earliest it can be done optional - could be used to create future tasks
• Priority

Recurring tasks Things we want done on some schedule. Will have the same info as one off tasks plus time that they should be rescheduled for when they are completed. Do we want time of day filters for recurrance for things that are only needed some of the time?

Task list List of tasks sorted by priority then deadline then creation time.

I have thought of doing something more complicated to bump up priority for things that are past deadline but I think that is better handled manually by volunteer manager making call if something that's been languishing at the bottom of the list is actually now more important than things above it in the list.

I think task list should be publicly visible with redirect to login (or create account) when picking up a task if not already logged in.

Task states not yet doable Earliest doable is in the future. Should be visible in admin view for editing but not on task list for volunteers. to do Waiting for someone(s) to pick up the task. Will be shown on task list. assigned Tasks that someone has picked up. Should be top of the list with details expanded for anyone with an active assigned task. If number of people assigned is less than number of people required then will still be shown in task list. Once there are enough people assigned only show it on task list for the people assigned. Want support for admin to assign tasks to other people: if someone doesn't have a device handy to interact with the list themselves then they can call or go to volunteer desk and we can give them things to do.
Complete Admin or one of the people who picked up the task can mark it as complete. For recurring tasks this triggers creation of the next in the series.

Assigning more than 1 task I'm leaning towards system enforcing an only one incomplete task assigned to a volunteer at a time. But not entirely sure on that; it might make sense to pick up multiple tasks that can be done together?

Tasks counting as having volunteered for ticket voucher for next time? Do we want doing tasks from this system to earn volunteer ticket voucher for next EMF? Do we want more than having done a task as minimum bar for that? Do we need something to capture complexity/effort of tasks so (un)plugging once cable doesn't count the same as

[wlcx]

I think a duplicate/expanded version of #1244

[russss]

This is also quite similar to emfcamp/orga#160 although there's arguably a difference between tasks which can be done by volunteers vs those which need handling for specific people. I'd prefer not to have multiple systems doing very similar things.

[russss]

I think this quite is a lot of work to do right and I don't think we should be reinventing the wheel ourselves this year. There's still a lot of web work to be done and I'm very hestiant to add to it at this point.

[will-h]

Basic attendee-reported problems a la c3bottles ("scan this QR code to report an infrastructure problem") would be a massive step forward. Lots of things with simple fixes which could have been quickly resolved in 2022, but we only heard about them later...