Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better voucher count calculation #566

Closed
MichiK opened this issue Jan 1, 2019 · 3 comments
Closed

Better voucher count calculation #566

MichiK opened this issue Jan 1, 2019 · 3 comments
Labels
Priority: Low This is not urgent. Status: Available Grab this issue and fix it! Status: Completed This issue is fixed. Type: Feature An idea for a new feature

Comments

@MichiK
Copy link
Contributor

MichiK commented Jan 1, 2019

Currently, the number of vouchers which an angel should receive is only determined by the count of shifts worked. This works well in cases where all shifts are of the same length and each and every shift counts equally. Meanwhile, the food voucher situation on congress became more complex:

  • Shifts are of different lengths (talk-related shifts are usually shorter than 2 hours, some coordinator shifts are up to 4 hours long)
  • Only shifts starting no earlier than a specific date/time count for vouchers (buildup shifts to not count during congress as food is free during buildup)
  • Angels can get a maximum of 3 vouchers a day (starting with the day they were marked as arrived, they worked for the first time or the earliest voucher-eligible date - whichever comes latest)
  • We now have not only shifts but also work log entries (I haven't checked if these count for vouchers or not)

This makes voucher calculation complex for shift coordinators and angels might be confused because it is not very easy for them to figure out if they may get vouchers or not, and if yes, how many.

Configuration should include:

  • hours per voucher
  • earliest voucher time
  • max. vouchers per day
@MyIgel MyIgel added the Type: Feature An idea for a new feature label Apr 21, 2019
@msquare msquare added Priority: Low This is not urgent. Status: Available Grab this issue and fix it! labels Apr 22, 2019
@MyIgel MyIgel added the Status: Needs discussion Additional discussion/feedback is needed label Sep 7, 2019
@Wiiilmaa
Copy link

It should also be possible to configure Workload Entries as eligible for Vouchers.

@Blue-Box
Copy link

Blue-Box commented Jan 5, 2020

@MyIgel I believe this issue has been resolved during the 36C3 with an update?

@MyIgel
Copy link
Member

MyIgel commented Jan 5, 2020

Except the point that there is a hard limit (for example 3 vouchers/day) but thats imho optional (but can be discussed further)

@MyIgel MyIgel closed this as completed Jan 5, 2020
@MyIgel MyIgel added Status: Completed This issue is fixed. and removed Status: Needs discussion Additional discussion/feedback is needed labels Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low This is not urgent. Status: Available Grab this issue and fix it! Status: Completed This issue is fixed. Type: Feature An idea for a new feature
Projects
None yet
Development

No branches or pull requests

5 participants