UI Clinic 17 NOV 2022: Minutes of the UI meeting (see minutes notes):

We agree that it makes sense to combine this request with FR Improvement of mail system and mail creation, i.e. the intermediate screen with selection should be omitted. Currently, the following solutions are proposed:

Proposal 1

• Below the "To field" there are two radio buttons "All users" / "Individual roles", with "Individual roles" the local roles of the course are listed individually.
• Advantage: It is clearly written that the mail will be sent to all users if this option is selected.
• Disadvantage: The decision process for users is more complex (nesting of options).

Proposal 2

• The button "Mail to Members" is interpreted as the most frequent use case (user wants to write to all users of the course). I.e. after clicking the button "Mail to Members" all local roles are already entered in the To field. An additional button "Local roles of the course", which works like "My Groups", lists all local roles at this point, you can deselect individual roles (suggestion: by default all roles are already preselected, because they were already entered in the To field). This way, roles can be removed from the To field that one does not want to write to. After accepting the change, you will be redirected back to the draft mail (all changes from before should be kept, the new selection for the To field will be accepted).
• Advantages: simpler decision (by default, a mail is sent to all users), workflow for button already exists with other buttons, most frequent user scenario is directly addressed (mail to all users).
• Disadvantage: The button "Local roles of the course" may be more likely to be overlooked.
  

Independently of both proposals, there needs to be a discussion about the language variables of the buttons (table of the course is called "Course Participants", tab is called "Members", button is called "Mail to Members"). This should be looked at with the language group. Similarly, in the above suggestions, the names of the buttons are not definitive and still need to be defined so that the user understands the action behind them well.

Next steps

We recommend to create short mockups for both suggestions (can also be low-level mockups) and to check them with max. 5 users (how do you understand one or the other screen) to find out if users prefer one variant or if there are problems with one or the other variant that have not been considered yet. Afterwards, this adaptation (suggestion) should be discussed with the maintainer before going into the JF and suggesting this adaptation (reference to the related request is important).