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
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. We have this system, it would be great to automate it here
Describe the solution you'd like
A clear and concise description of what you want to happen. Add in settings alongside "Auto-assign chairman for closing prayer" this option
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Since the local methods for assigning different parts to brothers vary significantly, our general approach is to avoid programming too many specific rules for every unique use case, in order to keep the code and interface clean and clear. However, we believe this scenario could be implemented by introducing a select field with all the usual meeting parts, allowing users to select a default person to assign the prayer. This way, the prayer part can be ‘linked’ to whoever has the selected meeting part assigned, and the app and its algorithms will account for that. Here’s the concept:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. We have this system, it would be great to automate it here
Describe the solution you'd like
A clear and concise description of what you want to happen. Add in settings alongside "Auto-assign chairman for closing prayer" this option
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: