Mon, Dec 4
The Questions for Participant section is collapsed by default because it's optional and can make the form look longer than necessary. Plus, as we add more questions, it could become the longest section in the form. An optional section shouldn't make the overall form appear more complex to users. Meeting a long-form makes users overwhelmed and discouraged from completing it.
Fri, Dec 1
Thu, Nov 30
Design Progress Update
Fri, Nov 24
Mon, Nov 20
Thu, Nov 16
Wed, Nov 15
Thu, Nov 9
Wed, Nov 8
- For the copy, go with the copy in the build.
Nov 2 2023
Oct 26 2023
UI Task in order of priority
Oct 24 2023
@Daimona If the number of participants who answered the affiliate question or the number of responses, 20 yes 20 no, don't change after people cancel their registration, why can't we leave the 'No responses' value the same after registrations are canceled?
Oct 20 2023
Current iteration on Event Invitation - Mobile web (Work in progress)
@Daimona what do you think of using 'Less than or equal to X' for the No responses scenario you described?
@Daimona my recommendation was for only numbers not percentages. So we can use Less than X for numbers only
Oct 19 2023
Latest design exploration on event invitation
Constraining ourselves to the character length limit and normal functionality of echo notifications. The echo notification could look like this:
2b. For events using the Event registration tool
Event Invitations within the Event registration tool
Oct 18 2023
@Daimona In the future, the form may become longer and will need to be further broken down into more sections. It would be cluttered to have many such rectangles. We can explore this at that time or if another need requires it.
Oct 17 2023
@gonyeahialam The text is inconsistent with regular styling, the light grey is usually reserved for disabled text or help text. can we agree that it will not be grey and instead the standard black?
The color I am using is the color for subtle text #54595D/Gray600/Base 20. The disabled color is #72777D/Gray500/Base30. But since this text is for an action and clickable you can go ahead to use the standard black (#202122/Gray700/Base10) so it is not confused as disabled.
Oct 13 2023
Any range, whether it is for the options or 'No response' that starts from zero as in <5 or 0 ≤ x ≤ 8 we use Less than 5, Less than 9(or whatever the number is)
If the lower range is above zero as in 8 ≤ x ≤ 16 we use Between 8 and 16
Oct 10 2023
Oct 9 2023
We would need to modify the description/helper text above to clearly inform organizers to only input the numbers.
If organizers are not used to using the numbers alone, the chances of the organizers making mistakes will increase
Is "Event details: Sandbox/VWalters..." the email subject?
Oct 6 2023
Oct 4 2023
Oct 3 2023
I am working on adding Grant ID to event details but I am a bit stuck on finding the most appropriate logo. @ifried would like your feedback on the logo.
I think this text is confusing, since "past" and "future" are not defined: "Past event dates cannot be changed to future dates to protect participant data." We can rewrite it to something like: "The event has ended, so you cannot change the event dates to future dates. This restriction protects participant data." This is lengthier, but perhaps more helpful in actually conveying the behavior to organizers. What do you all think? Curious to hear other opinions, especially from @gonyeahialam.
@cmelo 80vh is good.
Sep 28 2023
@ifried Does the last AC "The grant ID should not be displayed in the event page user interface. It should only be viewable in the organizer view when configuring or editing registration." also mean that the GrantID wouldn't show up in the organizer view of the event details page?
I have updated the design to include the correct format of the grant ID as a placeholder text in the form field "e.g. G-RF-1201-3302". @ifried Can the acceptance criteria be updated to include this?
Sep 25 2023
@ifried what is the reason for this AC "The grant ID information should be entered as freeform text"? Does the GrantID have a fixed format?
Sep 22 2023
The error message due to the Flux API ('There was an issue with validating the grant ID. Please try again later.') isn't clear enough on the next steps for the user. Should they pause filling it and come back later to try again? Do they clear the field, submit the form, and come back to edit it and see if the ID goes through? This can leave the user frustrated.
A better message might be:
There was an issue with validating your Grant ID. You can try submitting the form again in a few minutes. If the issue persists, you can still submit the form without a Grant ID and add it later by editing the event details.
Yes. it can be the last field in the Event details section of the form. I can work on it next.
Sep 21 2023
@Daimona The predefined error message shows when you submit the form and not when the field turns red immediately after you enter a future date.
Also, the pre-defined error message is for when you input an earlier date. I don't think there is one for when you input a future date
Sep 20 2023
@Daimona suggests we disable future dates in the calendar picker instead and show a notice message explaining why always. This prevents the user from making the error in the first place.
Decision(Design/Eng Meeting): Remove the limit from the message body and keep 200 character limit on the subject
Since separate tickets have been created for the changes, I am moving this to product sign-off.
Sep 19 2023
Also, the title in the build says Multiple organisers, the title is supposed to be the event name
The build is correct. This page was updated for the Participant questions feature/tasks.
- The Message participants button should be disabled (gray button) if the organizer does not have an email. The tool tip copy is correct, but right now it is on click of the button - @gonyeahialam can you clarify if this tooltip should appear on click or on hover of the disabled button?
If we leave the button disabled then the tooltip will only show on hover. However, we can leave it as it is in the build where the button isn't disabled and the tooltip shows on click.
- The To message participants... warning should go above the Recipients / Add recipients button
Yes, it is above. The warning is a central warning for the whole page.
- The Delete and Message participants buttons have a slight vertical alignment issue. When inspecting it you can see where it is off:
- The Delete button and the Message Participants button should not have any space between the buttons.
Yes, the buttons are together, the component is called a ButtonGroupWidget (destructive and progressive ButtonWidget)