Page MenuHomePhabricator

Generate & store invitation list when the form is submitted
Closed, ResolvedPublic3 Estimated Story Points

Description

As an event organizer, I want the invitation list to be generated and stored when I submit information into the form, so that it can identify audiences who may be good candidates to invite to my event.

Background: This ticket is one of three tickets that are a part of one stream of work. The first ticket is making the model triggerable by UI (T365628), the 2nd one is database access code (T366633), and the third one is the code to trigger the job and store the result using the previous tickets (which is this ticket). Note that the UI of the organizer inputting the information to generate the invitation list is handled by T356679, while the UI for handling the invitation list results is handled by T364804. The pending state after the request has been issued will be handled in T364802.

Testing notes: This will be testable either by querying the DB or going to SpecialInvitationList, depending on whether the SpecialInvitationList page is implemented in time.

Acceptance Criteria:

  • Given that a user has submitted a valid invitation list name and worklist on Special:GenerateInvitationList,
    • Then an invitation list should be generated
      • And the invitation list should be stored in the DB
    • And the user should be sent to Special:InvitationList for the newly created list

Event Timeline

ifried renamed this task from Generate & store invitation when the form is submitted to Generate & store invitation list when the form is submitted.Jun 5 2024, 4:25 PM
ifried removed the point value 3 for this task.
ifried set the point value for this task to 3.Jun 13 2024, 4:30 PM

Change #1051217 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] Store invitees after generating them

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

On second thought, this task really is blocked. The patch above is blocked on the creation of the schema (T366354). There's also one more patch I need to write which is blocked on both the creation of the schema, and the validation (T365629).

Daimona added a subscriber: gonyeahialam.

Also, @gonyeahialam just to confirm: from a user's perspective, what happens after they submit the form, assuming the submission is valid? Should we send the user to Special:InvitationList and show the pending state (T364802)?

Also, @gonyeahialam just to confirm: from a user's perspective, what happens after they submit the form, assuming the submission is valid? Should we send the user to Special:InvitationList and show the pending state (T364802)?

Yes

Change #1052140 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] Generate and store invitation list when special page form is submitted

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

Change #1051217 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] Store invitees after generating them

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

Change #1052140 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] Generate and store invitation list when special page form is submitted

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

vaughnwalters subscribed.

Acceptance Criteria:

  • Given that a user has submitted a valid invitation list name and worklist on Special:GenerateInvitationList,
    • ✅ Then an invitation list should be generated
      • ✅ And the invitation list should be stored in the DB
ce_invitation_list_usersce_invitation_lists
Screenshot 2024-07-16 at 9.03.20 PM.png (1×1 px, 515 KB)
Screenshot 2024-07-16 at 9.12.48 PM.png (612×1 px, 491 KB)
  • ✅ And the user should be sent to Special:InvitationList for the newly created list
    • Screenshot 2024-07-12 at 3.59.05 PM.png (380×1 px, 49 KB)
      ( Currently sent to Special:InvitationList, but the work is not yet complete to show the Invitation list )

All AC met, sending to product sign off.

This has been released to the beta cluster. Nothing explicitly user-facing to test, but I can see past invitation lists as a user, so data seems to be properly stored. I'm marking this as Done.