Okay, great, thanks. In that case, @gonyeahialam, perhaps you can update the designs based on this technical feedback?

So, in that case, the options would be to have a new form/new box OR to not make the participant sections collapsible? Would that be correct, @Daimona?

We will delay making a decision on how to handle the spacing issue in this ticket, and spacing changes will not be done in the scope of this ticket. This is because we plan to probably change how we display the clickwrap agreement in general very soon, since we want to allow organizers to choose which participant questions are included in their registration form.

Thank you, @gonyeahialam! I think this would be a great topic for a future design + engineering sync.

Hello @gonyeahialam, I have discussed this ticket with some members of the team, and I have decided that this is a high-priority design task to work on. This is because I think this would be a very useful feature for organizers, since some organizers would not want to ask any questions (or some of the questions) to their participants. In that case, could you add this ticket into your work for this week and beyond to develop some designs to determine how we could handle a scenario in which the organizer can pick which questions are a part of the event registration form? I see that there is also a design file link in this ticket, but I'm not sure if any work has already been done. Curious to hear your thoughts; thanks!

My mistake, this still needs to be worked on.

This work is done

Hello, @KEchavarriqueen! No, the project is not done yet, but we'll let you know when it is ready! What happened is that we finished one specific sub-task for the project, but the whole project itself is still in progress. When the whole project is done, we will close this ticket (T321814) and reach out to the Grants team.

This looks good as per QA notes, so I'm marking this as Done.

Thanks, @vaughnwalters! I have added your suggested rewrite of the post-MVP behavior into the ticket.

The documentation text looks great; I approve, @Daimona, and thank you for writing it!

I just talked about this with @MusikAnimal about how we can get a list of people who edited an article, and he provided some potential tools for us to look into (see his comment below):

We are closing this parent task, as the work to be done is included in the other clickwrap tasks.

I have updated the AC to allow the display of the Response Statistics tab, even if there is no data to display. This is because, when I see the example as shown in the comment above, I think it can be useful for the organizer to understand why they do not see data in this tab, as they may use the feature for multiple events and may expect to see the data due to having access to data in the Response Statistics tab in other events.

The feature has been released, so I am marking this as Done.

I have discussed this with @gonyeahialam, and he has highlighted that this is his priority for us to fix first because it would improve the user experience and it would be easier to implement than some of the other UX issues to fix, as outlined in T346968. For this reason, we can look into working on this soon.

Thank you, @gonyeahialam!

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

Thanks for providing this example, @vaughnwalters! It was helpful for me to see it in a test event.

@vaughnwalters, hello! Can you perhaps provide some examples of the inconsistencies in certain test events or some screenshots, so the issue can be a bit more clear to me? I want to make sure I understand it properly; thanks!

@gonyeahialam Hello! It looks like this task is the same as T340115 at this point (in terms of the AC). I can close it, correct?