Note that the implementation details will be informed by findings from T318378: Investigate emailing users in the context of global accounts

@gonyeahialam Hello! What are the updated prototypes for organizer messaging participants for this epic? Note that we do not need to include filters for PII support yet? Can you add the Figma link and screenshots directly into the ticket? Thanks in advance!

Change 888239 had a related patch set uploaded (by Mhorsey; author: Mhorsey):

[mediawiki/extensions/CampaignEvents@master] bug:T317223

https://gerrit.wikimedia.org/r/888239

Change 898806 had a related patch set uploaded (by Mhorsey; author: Mhorsey):

[mediawiki/extensions/CampaignEvents@master] bug: T317223

https://gerrit.wikimedia.org/r/898806

Change 888239 abandoned by Mhorsey:

[mediawiki/extensions/CampaignEvents@master] bug:T317223

Reason:

https://gerrit.wikimedia.org/r/888239

This is an exciting development.
Which table can be used to identify if a participant has an email address associated with their account? Will we be logging that in campaigns tables? Or is that something best referenced on another table? If another table, I would be grateful for that table information.
And where can I learn more about the campaigns tables where this campaigns email data will be logged/stored?

Change 898806 had a related patch set uploaded (by Mhorsey; author: Mhorsey):

[mediawiki/extensions/CampaignEvents@master] Implement email sending

https://gerrit.wikimedia.org/r/898806

Change 898806 had a related patch set uploaded (by Daimona Eaytoy; author: L10n-bot):

[mediawiki/extensions/CampaignEvents@master] Implement email sending

https://gerrit.wikimedia.org/r/898806

Change 898806 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] Implement email sending

https://gerrit.wikimedia.org/r/898806

✅ A selected list of participants can be sent an email by the organizer all at once via the 'email this user' feature QA note - because this is API testing, the participant list is sent just as an array of user IDs
✅ Only participants who have an email address associated with their accounts AND have checked 'All other users to email me' in Preferences should be available for email messages
🔴 The new API endpoint should be documented in https://www.mediawiki.org/wiki/Extension:CampaignEvents/Api. The documentation of the "exclude_user" parameter to the "List the participants of an event" endpoint should also be updated to reflect the new parameter name ("exclude_users").

✅ Email sends through API.
{F37143950}

✅ invert_users works correctly:
{F37143968}

A few notes on this:

🔴 For this AC:

The new API endpoint should be documented in https://www.mediawiki.org/wiki/Extension:CampaignEvents/Api. The documentation of the "exclude_user" parameter to the "List the participants of an event" endpoint should also be updated to reflect the new parameter name ("exclude_users").

There is no mention of exclude_user in the List the participants of an event endpoint. Does the AC need updated or does the api doc need to change?

🔴 In the API docs, if the CSRF token does not match, the API should return a 400 with The provided CSRF token does not match but right now it returns a 403 forbidden:
{F37143980}

🔴 In the API docs, if if the ID of the event does not exist, the API should return a 404 with The given ID does not correspond to an existing event registration but right now it returns a 403 forbidden:
{F37143954}

🔴 In the API docs, invert_users is listed as a required parameter, but when I omit that param, it defaults to true and sends the email instead of displaying an error that a required param invert_users is missing:

{F37143971}

🔴 In the API docs, user_ids is listed as a required parameter, but when I omit that param and also omit invert_users, it defaults to true and sends the email instead of displaying an error that a required param of user_ids is missing:

{F37143976}

Thanks @vaughnwalters

🔴 The new API endpoint should be documented in https://www.mediawiki.org/wiki/Extension:CampaignEvents/Api. The documentation of the "exclude_user" parameter to the "List the participants of an event" endpoint should also be updated to reflect the new parameter name ("exclude_users").

Done

🔴 For this AC:

The new API endpoint should be documented in https://www.mediawiki.org/wiki/Extension:CampaignEvents/Api. The documentation of the "exclude_user" parameter to the "List the participants of an event" endpoint should also be updated to reflect the new parameter name ("exclude_users").
There is no mention of exclude_user in the List the participants of an event endpoint. Does the AC need updated or does the api doc need to change?

The API doc is updated

🔴 In the API docs, if the CSRF token does not match, the API should return a 400 with The provided CSRF token does not match but right now it returns a 403 forbidden:
{F37143980}

This was a documentation error

🔴 In the API docs, if if the ID of the event does not exist, the API should return a 404 with The given ID does not correspond to an existing event registration but right now it returns a 403 forbidden:
{F37143954}

This has been fixed in T343201

🔴 In the API docs, invert_users is listed as a required parameter, but when I omit that param, it defaults to true and sends the email instead of displaying an error that a required param invert_users is missing:

This was a documentation error

🔴 In the API docs, user_ids is listed as a required parameter, but when I omit that param and also omit invert_users, it defaults to true and sends the email instead of displaying an error that a required param of user_ids is missing:

This was a documentation error

Change 944179 had a related patch set uploaded (by Mhorsey; author: Mhorsey):

[mediawiki/extensions/CampaignEvents@master] Resolve issues found in QA

https://gerrit.wikimedia.org/r/944179

Change 944179 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] Resolve issues found in QA

https://gerrit.wikimedia.org/r/944179

In T317223#9058641, @MHorsey-WMF wrote:

Thanks @vaughnwalters

🔴 The new API endpoint should be documented in https://www.mediawiki.org/wiki/Extension:CampaignEvents/Api. The documentation of the "exclude_user" parameter to the "List the participants of an event" endpoint should also be updated to reflect the new parameter name ("exclude_users").

Done

🔴 For this AC:

The new API endpoint should be documented in https://www.mediawiki.org/wiki/Extension:CampaignEvents/Api. The documentation of the "exclude_user" parameter to the "List the participants of an event" endpoint should also be updated to reflect the new parameter name ("exclude_users").
There is no mention of exclude_user in the List the participants of an event endpoint. Does the AC need updated or does the api doc need to change?

The API doc is updated

✅ this is now documented and is functioning correctly.

🔴 In the API docs, if the CSRF token does not match, the API should return a 400 with The provided CSRF token does not match but right now it returns a 403 forbidden:
{F37143980}

This was a documentation error

✅ correctly documented now:

🔴 In the API docs, if if the ID of the event does not exist, the API should return a 404 with The given ID does not correspond to an existing event registration but right now it returns a 403 forbidden:
{F37143954}

This has been fixed in T343201

✅ this is fixed now:

🔴 In the API docs, invert_users is listed as a required parameter, but when I omit that param, it defaults to true and sends the email instead of displaying an error that a required param invert_users is missing:

This was a documentation error

✅ Documentation is correct now

🔴 In the API docs, user_ids is listed as a required parameter, but when I omit that param and also omit invert_users, it defaults to true and sends the email instead of displaying an error that a required param of user_ids is missing:

This was a documentation error

✅ Documentation is correct now

one more thing here is the following response "user_is_valid_recipient": bool needs added to the List the participants of an event endpoint

In T317223#9070474, @vaughnwalters wrote:

one more thing here is the following response "user_is_valid_recipient": bool needs added to the List the participants of an event endpoint

{{done}}

all AC met, moving to product sign off