You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the Midburn event, the system administrator allocates appreciation tickets to all camps (Activity A),
and Camp Managers need to allocate appreciation tickets to the camp members (Activity B).
this process is currently possible but without any date frame control (meaning it is currently possible to edit the values year round).
Proposal: control the dates in which it will be possible to change the camp allocation (A), and members allocation (B) of appreciation tickets.
For example: suppose current event is M2017, and next event is M2018.
on M2017 Edit event page: we add 2 inputs for start and end period for appreciation tickets.
these dates will enforce the ability to change the camp allocation (A), and member allocation (B) - meaning it will only be possible to edit the values within the start and end period.
once the end dates passes the event form inputs fields are locked.
these allocations are later downloaded as csv and based on this output, M2017 member receive tickets for M2018.
feel free to correct/ update the requirements \ process.
Im missing Panda and Ori Bandel for this discussion I think we should add the to GIT.
The text was updated successfully, but these errors were encountered:
After the Midburn event, the system administrator allocates appreciation tickets to all camps (Activity A),
and Camp Managers need to allocate appreciation tickets to the camp members (Activity B).
this process is currently possible but without any date frame control (meaning it is currently possible to edit the values year round).
Proposal: control the dates in which it will be possible to change the camp allocation (A), and members allocation (B) of appreciation tickets.
For example: suppose current event is M2017, and next event is M2018.
these allocations are later downloaded as csv and based on this output, M2017 member receive tickets for M2018.
feel free to correct/ update the requirements \ process.
Im missing Panda and Ori Bandel for this discussion I think we should add the to GIT.
The text was updated successfully, but these errors were encountered: