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
As a manager I want to be able to ask helpers to provide certain information, when signing up a shift.
Some mandatory, others optional.
Examples could be "Full Name" (for checking during entering the facility) or drivers license.
Information type is either text (incl. numbers or dates) or boolean (existing or not).
This information shall be asked or confirmed from every person interested in signing up.
Whether it's taken from already stores attributes or entered manually is up to usability decisions.
I don't want to manually set up the requested information for every shift I create, because usually it's
bound to the task, this shift is created for.
It would be good, if the set of "asked for" attributes is assigned to the task and displayed with the shift.
Over time requested information can change, e. g. based on experiences. So it would be good if every shift
had a view of the exact information set known at shift creation time, so historical views on shifts don't show
new attributes.
Nonetheless as a manager there might be the need to change a shift attribute set, caused by new information
requirements, since shift was initially created.
Information entered or confirmed by helpers shall be stored with the assignment, so it's clear what's been the requested information and what was the response.
All the requested data are not for public viewing, but shall be presented to managers only, ideally as a list or table, aggregated per shift.
The text was updated successfully, but these errors were encountered:
As a manager I want to be able to ask helpers to provide certain information, when signing up a shift.
Some mandatory, others optional.
Examples could be "Full Name" (for checking during entering the facility) or drivers license.
Information type is either text (incl. numbers or dates) or boolean (existing or not).
This information shall be asked or confirmed from every person interested in signing up.
Whether it's taken from already stores attributes or entered manually is up to usability decisions.
I don't want to manually set up the requested information for every shift I create, because usually it's
bound to the task, this shift is created for.
It would be good, if the set of "asked for" attributes is assigned to the task and displayed with the shift.
Over time requested information can change, e. g. based on experiences. So it would be good if every shift
had a view of the exact information set known at shift creation time, so historical views on shifts don't show
new attributes.
Nonetheless as a manager there might be the need to change a shift attribute set, caused by new information
requirements, since shift was initially created.
Information entered or confirmed by helpers shall be stored with the assignment, so it's clear what's been the requested information and what was the response.
All the requested data are not for public viewing, but shall be presented to managers only, ideally as a list or table, aggregated per shift.
The text was updated successfully, but these errors were encountered: