1
2
Fork
You've already forked treehouse
1

Common Prep team and service lead #234

Open
opened 2025年04月18日 15:08:01 +02:00 by rhogue · 1 comment

At the meal lead meetup we talked about different ways of wanting to organize our prep teams - and how this would be different on a per meal basis.

A feature request is to allow the meal lead to select how many meal prep and service lead people they want - for example:
one meal, the meal lead may choose assemble their own team so they do not need anyone to sign up as prep or service lead, so they would enter 0 in the box for number of meal prep and number of service leads.

Another meal might be prep intensive, in which case the meal lead might actually request 3 helpers for meal prep.

In the case of service leads, I think we should allow 0, 1, or 2 depending on the number of sittings.

This flexibility on a per-meal basis would support meal prep teams which is an idea that is forming, but also would support things working the way they are now, which works well for some meals and is a preference for some of the meal leads.

At the meal lead meetup we talked about different ways of wanting to organize our prep teams - and how this would be different on a per meal basis. A feature request is to allow the meal lead to select how many meal prep and service lead people they want - for example: one meal, the meal lead may choose assemble their own team so they do not need anyone to sign up as prep or service lead, so they would enter 0 in the box for number of meal prep and number of service leads. Another meal might be prep intensive, in which case the meal lead might actually request 3 helpers for meal prep. In the case of service leads, I think we should allow 0, 1, or 2 depending on the number of sittings. This flexibility on a per-meal basis would support meal prep teams which is an idea that is forming, but also would support things working the way they are now, which works well for some meals and is a preference for some of the meal leads.

@rhogue Done! Two fields added in the meal form (see screenshot)

That said, I disabled these fields when updating an existing meal. Which means that, for now, we can't change the number of meal preps or service leads once the meal has been created in the system.

That will require a bit more work. So I'll keep this issue open to keep that on my radar.

@rhogue Done! Two fields added in the meal form (see screenshot) That said, I disabled these fields when updating an existing meal. Which means that, for now, we can't change the number of meal preps or service leads once the meal has been created in the system. That will require a bit more work. So I'll keep this issue open to keep that on my radar.
Sign in to join this conversation.
No Branch/Tag specified
main
review-meal
concert-mailing-list
email-community-fund
add-remove-from-funds
ledger
clean-up-reminder-email
no-take-out
delete-booking
free-night
open-concerts
more-concert-2
concert-admin
car-share-whitelist
more-concert
more-car-admin
concert
meal-setting-clean-up
car-share-admin
car-payment-fund
fix-car-fund-relationship
documentation
new-farmer
add-library-item
croppie
simplify-meal-system
implement-meal-role
team-members-in-db
settigs-class
library-v1
various-fixes
seating-size
tool-library-6
meal-associations
kamal
extract-tve-meals-features
dev_setup_script
checkout-checklist
tve-controller
split-admin-controller
tve-override
scottd-dev-setup
195-meal-team-members
leftovers
sqlite-dev
multiple-seatings-1
multiple-seatings-2
google-api
portion-name-desc
data-integrity
upgrade-ruby
gem-upgrade
finish-car-booking-payment
car-booking-payments
admin-meal-payments
meal_payments
eggs-page
description-for-transfers
area-booking-max-limit
upgrade-ch-area
areas-part-3
add-remove-money-admin
manage-rooms
last-details-around-meal
close-meal-service
refine-transfers
eb-household-and-attendees
add-fund-email
meal-sign-up
add-state-to-payments
meal-screens
add-children
meal-models
66-transaction-table
66-create-tabs-for-funds
66-create-fund
add-bookings-to-car-page
note-for-car-bookings
car-owner
open-car-sharing
update-room-booking
room-booking-to-use-dates
collapse-cars
prepare-car-booking
charging-color
a-round-of-refactor
ajax-for-car-booking
fix-car-booking
add-columns-to-car-and-booking
car-sharing-algorithm
ajax-calls
reorganize-secrets
create-car-booking
master
car-calendar-color
book-a-car
remove-user
update-packages
fix-booking-confirmation
open-marketplace
pricing-options
add-cron-for-emails
19-ten-day-booking
19-some-rules-for-booking
feedback-from-becky
19-emails-and-guest-room-admin
19-pay-by-night
19-create-payments
19-ten-days-credit
19-household-name-logic
19-room-booking-confirmations
19-create-households
19-guest-room-admin
19-users-roles-table
marketplace-search
add-tests
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
etienne/treehouse#234
Reference in a new issue
etienne/treehouse
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?