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!

In T321814#9273065, @ifried wrote:

Hello @cmelo! I have updated the AC; thanks for catching that! The grant ID should only be viewable in the UI for the organizers of the event, but it should not be viewable by non-organizers. It can be viewable by the organizers when configuring registration, when editing registration, or on the EventDetails page.

Hi @ifried and @gonyeahialam could you tell me which one is right, we have on the AC the following sentence:

In T321814#9250833, @Rmaung wrote:

@gonyeahialam just to flag (and I think this is a mistake that originated with me) the grant ID has an extra digit (so the copy would read "For example, if your grant ID is G-1111-11111, please enter 1111-11111." @cmelo can you confirm?

Hi @ifried and @gonyeahialam I would like to check with you on the grant ID format we will ask the organizer to provide, for what I saw in the designs on the tasks, it says:

Hi @gonyeahialam, we are having a conversation about how the height of the list of participants will look like, could please tell us which one do you prefer, we end up with 2 options, 70vh or 80vh, here are some screenshots, so you can see how they would look like?

Second: why is this the case? The message clearly states «This is only applicable if ...», and that's how it works in practice, i.e., the action can be undone if there are no answers. Then why are we always showing this message? The lack of a written rationale makes me wonder if this part of the AC is outdated or something like that.

In T339979#9181903, @gonyeahialam wrote:

In T339979#9180881, @ifried wrote:

Yeah, I hear you, @gonyeahialam. I was basically trying to do a few things to improve the sentence, which were:

• change from "can't" to "cannot" (since "can't" is a bit informal)
• change from "the future" to "future date," since I thought it was a bit more clear
• change "ensure participant data safety" to "protect participant data" since I found it a bit more accurate & clear

Do you agree with any of the choices I made above?

If yes, what do you think of this rewritten version (see below)?:

"Past event dates cannot be changed to future dates to protect participant data."

Yes. This is better. It combines the strengths of the two above.

@ifried We need to update the AC for this task.

In T339979#9169451, @gonyeahialam wrote:

In T339979#9165859, @cmelo wrote:

Given the new acceptance criteria:
Organizers can change the start and end date of an event to be a date in the past after the event ends, but they cannot change it to be a date in the future after the event ends

We are no longer disabling the date fields anymore, but we will still show an error message in case the organizer tries to change the end date to be in the future.

This also means that we no longer need this message, or should change its text to inform that:
The end event date end time cannot be changed to a date in the future .... :

@gonyeahialam could you update the prototypes to reflect it please, thank you!

I would do that @cmelo. Where can I read the details/rationale behind this decision? This will help me craft the error message.
Also, the 2nd and last AC bullet points seem to be contradicting each other. I think the 2nd AC should be removed.
2nd AC: Organisers would be prevented from changing the event date of an event that has already ended
Last AC: Organizers can change the start and end date of an event to be a date in the past after the event ends, but they cannot change it to be a date in the future after the event ends

Given the new acceptance criteria:
Organizers can change the start and end date of an event to be a date in the past after the event ends, but they cannot change it to be a date in the future after the event ends