In T362686#9722647, @DAlangi_WMF wrote:

@Daimona, I was already working on a patch on the road to resolve these kinds of DB related issues and I included the solution to this issue in the patch. Let me know if the issue gets resolved for you locally with this patch, then you can review and do the honors :)

@Daimona LGTM too

@vaughnwalters

❌ And this new error should be documented on mediawiki.org
@cmelo The error message Please email participants on XXX, the wiki where the event was created. needs to be added to the [[

@vaughnwalters

❌ And this new error should be documented on mediawiki.org
@cmelo Please set organizers on arwiki, the wiki where the event was created needs to be added to the Register as a participant documentation on mediawiki.org

❌ And this new error should be documented on mediawiki.org
@cmelo Please delete your event registration on XXX, the wiki where the event was created. needs to be added to the Delete a registration documentation on mediawiki.org

THank you @Krinkle and @Daimona, and sorry for the delay on this.

Hi @vaughnwalters just a note, on this task the changes were more technical changes on the code base, but it basically involves how we communicate with the DB, same for T360517, so the tests I think you could do here could be a general check on every special page to check it the data is being correctly shown.

Hi @vaughnwalters, I was able to fix both issues.

Hi @ifried I am wondering if I should hide the chat or not because the AC says:
They should see the view that all users see (i.e., not organizer view) with only the EventDetails & Participants tab

In T324259#9640185, @vaughnwalters wrote:

✅ This is working correctly and acceptance criteria is met in both Special:EditEventRegistration/{eventID} and Special:MyEvents (Kebab menu "Edit Registration")

---

@cmelo two things though:

1. The linked text should be a stronger font weight. Note the difference between the comp and the build :

comp	build

2. I noticed on spanish betacluster that the url was not linked. I am assuming this is a limitation of the translation (or possibly just because it hasn't been translated yet), but wanted to check with you here to make sure.

In T354880#9620217, @Daimona wrote:

@ifried The following two scenario have been brought up in code review and would require further thought:

Scenario 1

• On day X, 20 people answer all PII questions.
• On day X + 80, the organizer removes all PII questions from the event (potentially by mistake, but we can't know that)
• On day X + 90, the initial 20 answers get deleted, but not aggregated because the questions are no longer enabled
• On day X + 92, the organizer enables PII questions again

The way it currently works in the proposed patch is that the organizer will not see aggregated data for the initial 20 answers. Should this be the case?

Scenario 2

• On day X, 20 people answer all PII questions.
• On day X + 90, the initial 20 answers get aggregated
• On day X + 100, the organizer removes all PII questions from the event

When the event ends, the organizer would still be able to see aggregated data for the initial 20 answers, even if the question is no longer enabled. However, the aggregated data would not include any answers given after day X + 10 (i.e., answers that haven't been aggregated by the time the organizer removes PII questions).

---

We aren't sure what to do in these scenarios, as it's ultimately a product question, and I'd like to hear your opinions on these.

Yes, I also think that it is a good idea to remove whitespace.

Here are the special pages we have on our extension and the reason in my opnion why it shoud be redirected or not:

Documentation of the List the participants of an event endpoint updated.

In T349332#9280818, @ifried wrote:

I am discussing this with @gonyeahialam now, and here is what we have decided:

• For the MVP, we can release with the current behavior, which is that the non-PII data is no longer viewable in the Participants tab after the event ends and it only displays as a range in the Statistics tab after the event ends if there are at least 10 responses. This is because, while it is not an ideal user experience, it conforms to the current data retention policies of the feature and it does not reveal any data that should be hidden to the organizers. Furthermore, it does not create any issues with the data accuracy. However, we may explore improving this experience after the MVP release (see recommended behavior below).
• After MVP, the recommended behavior is: We should always display all of the non-PII data in the Participants tab, including after an event ends. The statistics tab should show the exact number of responses for the non-PII data. This data would always be viewable in the Statistics tab, once the event ends.
  • For this to work to be done, we would need to change the data retention policy for non-PII data, so it does not get deleted within 90 days or when the event ends. We can discuss this with internal stakeholders in the future.

How does this sound, @vaughnwalters, @Iflorez, @cmelo, and any others? If this works for people, I can create a follow-up task or edit this task to look into potentially changing the data retention for non-PII in the future. Thanks in advance!