As an organizer, I want to be able to assign different roles to fellow organizers in my campaign, so that I can delegate work with greater efficiency and so that I can ensure that trusted organizers are managing more complex or sensitive tasks.
Acceptance Criteria:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T368951 [EPIC] Miscellaneous improvements to Event Registration experience | |||
| Open | None | T316406 Create the ability to assign different organizer roles |
@ifried I know this is a V2 task, so not something we should be working on now, but I have an important question that may change things for V1 DS. Reading the task description, I'm assuming that it is about different organizer roles that are valid for all events. Something like user groups: if you are added to (say) the "advanced organizer" group, that remains valid for all events.
But IIUC, we also have organizer roles that are only valid for a single event. For instance, I may not be in any organizer-related user group, but I could be the main organizer for an event, or a secondary organizer, or another kind of organizer with limited responsibility only for that event.
Can you confirm whether these are indeed separate feature and which versions they'll be worked on? Also, if they are indeed distinct feature, I'd suggest renaming this one to something else than "roles" to avoid any possible confusion.
@Daimona Thank you for sharing this thoughtful breakdown! Yes, I would need to collect more feedback from organizers, but I think that 'general organizer' and 'advanced organizer' apply to all events. However, 'trainer' applies to the specific event, since it is not so much about specific rights but more about assigning a specific role that is important for organizers to determine in advance and would be useful to share with participants (so they know who will be training them/who already conducted a training if they have any questions related to training). I can break this down into two subtasks: one for the general user groups that apply to all events, and the other for roles that are specifically tied to a campaign. Does that sound good?
Thanks for the clarification! I don't think we need to break this down right now, I just wanted to make sure that the two were different features, because in the code and DB we already have the concept of per-event roles, and I wanted to make sure that we still needed it.
Yup, makes sense. We should definitely keep per-event roles in the code. Much appreciated!