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
Elternzugang 1-3: Anmelden an einem Anlass #1967
Closed
39 of 51 tasks
ThomasEllenberger opened this issue
Jan 4, 2023
· 1 comment
· Fixed by hitobito/hitobito_youth#30 or #2094
Closed
39 of 51 tasks
Elternzugang 1-3: Anmelden an einem Anlass #1967
ThomasEllenberger opened this issue
Jan 4, 2023
· 1 comment
· Fixed by hitobito/hitobito_youth#30 or #2094
Milestone
Comments
ThomasEllenberger
changed the title
Elternzugang 1-3: Kind anmelden an einem Anlass
Elternzugang 1-3: Anmelden an einem Anlass
Jan 4, 2023
10 tasks
carlobeltrame
added a commit
that referenced
this issue
Apr 13, 2023
carlobeltrame
added a commit
to hitobito/hitobito_youth
that referenced
this issue
Apr 14, 2023
This allows us to easily define abilities which parents can inherit from their children. I.e. if the child is allowed to do it, the parent is also allowed to do it. Refs hitobito/hitobito#1967
carlobeltrame
added a commit
that referenced
this issue
Apr 14, 2023
carlobeltrame
added a commit
to hitobito/hitobito_youth
that referenced
this issue
Apr 14, 2023
This allows us to easily define abilities which parents can inherit from their children. I.e. if the child is allowed to do it, the parent is also allowed to do it. Refs hitobito/hitobito#1967
carlobeltrame
added a commit
to hitobito/hitobito_youth
that referenced
this issue
Apr 14, 2023
This allows us to easily define abilities which parents can inherit from their children. I.e. if the child is allowed to do it, the parent is also allowed to do it. Refs hitobito/hitobito#1967
carlobeltrame
added a commit
to hitobito/hitobito_youth
that referenced
this issue
Apr 14, 2023
carlobeltrame
added a commit
to hitobito/hitobito_youth
that referenced
this issue
Apr 14, 2023
…ageds Most of the changes here can use the new for_self_or_manageds mechanism. But when a condition combines her_own_or_something_else, then we must manually add the manager option, to make sure that the manager only inherits the her_own part, not the something_else part. Refs hitobito/hitobito#1967
carlobeltrame
added a commit
to hitobito/hitobito_youth
that referenced
this issue
Apr 14, 2023
carlobeltrame
added a commit
to hitobito/hitobito_youth
that referenced
this issue
Apr 14, 2023
…ageds Most of the changes here can use the new for_self_or_manageds mechanism. But when a condition combines her_own_or_something_else, then we must manually add the manager option, to make sure that the manager only inherits the her_own part, not the something_else part. Refs hitobito/hitobito#1967
Closed
15 tasks
TheWalkingLeek
pushed a commit
that referenced
this issue
Apr 28, 2023
This was referenced Apr 28, 2023
TheWalkingLeek
pushed a commit
that referenced
this issue
May 1, 2023
mtnstar
pushed a commit
that referenced
this issue
May 3, 2023
carlobeltrame
added a commit
to hitobito/hitobito_youth
that referenced
this issue
May 12, 2023
This allows us to easily define abilities which parents can inherit from their children. I.e. if the child is allowed to do it, the parent is also allowed to do it. Refs hitobito/hitobito#1967
carlobeltrame
added a commit
to hitobito/hitobito_youth
that referenced
this issue
May 12, 2023
carlobeltrame
added a commit
to hitobito/hitobito_youth
that referenced
this issue
May 12, 2023
…ageds Most of the changes here can use the new for_self_or_manageds mechanism. But when a condition combines her_own_or_something_else, then we must manually add the manager option, to make sure that the manager only inherits the her_own part, not the something_else part. Refs hitobito/hitobito#1967
Noch offen: Manuelles Durchtesten aller obiger Use Cases. |
18 tasks
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Teilissue von #603.
User Story
Wenn ich als Verwalter*in durch einen externen Link, oder in Hitobito auf einen Anlass/Kurs/Lager gelange, will ich dort auswählen können wen ich zu diesem anmelde. Mich, oder einen durch mich verwalteten Account.
Dabei will ich nicht Account wechseln müssen und will ohne auf einen anderen Account wechseln zu müssen auch mehrer Personen nacheinander anmelden können (mehrere Kinder, oder mich und mein Kind).
Anforderungen
Anmeldung an einen Anlass
• Direkt auf dem Anlass
• Anlass/Kursliste auf Gruppe
• Anlass-Liste (links im Menu /list_events)
Mockup
Tech-Spec
Ability.new(child).can? :create, participation
und dann in der participation_ability.rb im Core Regeln dafür ergänzen, die die bisherigen Regeln voncan? :show, event
wiederspiegeln.user
berücksichtigt, sondern auchuser.manageds
. Ich stelle mir etwas im folgenden Stil vor:ToDo
permission(:any).may(:create).her_own_if_application_possible
muss im Core angepasst werden, damit sie miteinbezieht, ob die betroffene Person den Anlass überhaupt anzeigen darf. Beispiel für Delegation an eine andere Ability. Am besten gleich so implementieren:Ability.new(participation.person).can? :show, event
, nicht mituser
odercurrent_person
oder so arbeiten, weil es so im Youth Wagon einfacher zu erweitern ist.user
berücksichtigen, sondern auchuser.manageds
:permission(:any).may(:show).in_same_layer_or_globally_visible_or_participating
class_side(:list_available).if_any_role
(falls der Elternteil keine Rollen hat aber das Kind schon, soll der Elternteil trotzdem Anlässe auflisten können)her_own
Bedungungen jeweils nicht nuruser
berücksichtigen, sondern auchuser.manageds
:permission(:any).may(:show).her_own_or_for_participations_read_events
permission(:any).may(:show_details, :print).her_own_or_for_participations_full_events
permission(:any).may(:create).her_own_if_application_possible
participation.person
in[user, *user.manageds]
enthalten ist, und andererseits muss weiterhin mitAbility.new(participation.person).can? :show, event
geprüft werden, ob das Kind selber den Anlass sehen dürftepermission(:any).may(:destroy).her_own_if_application_cancelable
general(:create).at_least_one_group_not_deleted
(falls der Elternteil keine Rollen hat aber das Kind schon, soll der Elternteil trotzdem Anlässe auflisten können.) Falls das nicht möglich ist, muss möglicherweise diesergeneral
Constraint im Core in alle normalenpermission(...).may(:create)
eingebaut werden, und dann im Youth Wagon entsprechend für sich selbst und für alle Manageds erlaubt werdenher_own
Bedungungen jeweils nicht nuruser
berücksichtigen, sondern auchuser.manageds
:permission(:any).may(:show_priorities, :show_approval).her_own
her_own
Bedungungen jeweils nicht nuruser
berücksichtigen, sondern auchuser.manageds
:permission(:any).may(:decline).own_invitation
her_own
Bedungungen jeweils nicht nuruser
berücksichtigen, sondern auchuser.manageds
:permission(:any).may(:show, :update).her_own
Ability.new(person).can? :create, hypothetical_participation_for(person)
können, also die sich selber für den Anlass anmelden könntenAbility.new(person).can? :destroy, participation
erlaubt istThe text was updated successfully, but these errors were encountered: