Change Details

#### User story As Campaigns' designer, I want to test multiple interaction behaviors for the event type selector—including how “Other” is handled when selected alone or alongside other options—so that we can identify which version provides the most intuitive and user-friendly experience, and implement the one that best supports clarity and ease of use. #### Background In {T355253}, there has been discussion on how we can handle the 'Other' selection when selecting Event types in the Event Registration form, since: → If we allow Other, we don't want organizers to pick a second event type. If they do, it kind of defeats the purpose of Other. → We want that organizers can pick only 1 option for Other (i.e., Other) but a maximum of 2 options for event types. We have suggestions for that behavior: - Having an 'Other' header with 'Other' as an option (may feel redundant, and unclear). - Separate the 'Other' option with a border, and have a description on the item that mentions the behavior (i.e permitting a single selection only if you select 'Other') - No headers at all + item description - No headers at all (items ordered alphabetically) - When the user selects an event, the 'Other' option is disabled and/or when the user selects 'Other', all of the other event types get disabled. ####Intended audience While organizers (who use Event Registration) are the intended audience for this selection process, we can test on general audiences (i.e., not organizers specifically) since we aim for general usability. #### Acceptance criteria [] User script is drafted [] At least 5 user testing sessions are conducted using Userlytics as platform [] Observations are collected [] A summary of insights is documented [] A final recommendation is made based on findings, outlining which option should move forward for implementation, and why.

#### User story As Campaigns' designer, I want to test multiple interaction behaviors for the event type selector—including how “Other” is handled when selected alone or alongside other options—so that we can identify which version provides the most intuitive and user-friendly experience, and implement the one that best supports clarity and ease of use. #### Background In {T355253}, there has been discussion on how we can handle the 'Other' selection when selecting Event types in the Event Registration form, since: → If we allow Other, we don't want organizers to pick a second event type. If they do, it kind of defeats the purpose of Other. → We want that organizers can pick only 1 option for Other (i.e., Other) but a maximum of 2 options for event types. We have suggestions for that behavior: - Having an 'Other' header with 'Other' as an option (may feel redundant, and unclear). - Separate the 'Other' option with a border, and have a description on the item that mentions the behavior (i.e permitting a single selection only if you select 'Other') - No headers at all + item description - No headers at all (items ordered alphabetically) - When the user selects an event, the 'Other' option is disabled and/or when the user selects 'Other', all of the other event types get disabled. ####Intended audience While organizers (who use Event Registration) are the intended audience for this selection process, we can test on general audiences (i.e., not organizers specifically) since we aim for general usability. #### Acceptance criteria [x] User script is drafted [] At least 5 user testing sessions are conducted using Userlytics as platform [] Observations are collected [] A summary of insights is documented [] A final recommendation is made based on findings, outlining which option should move forward for implementation, and why.

#### User story As Campaigns' designer, I want to test multiple interaction behaviors for the event type selector—including how “Other” is handled when selected alone or alongside other options—so that we can identify which version provides the most intuitive and user-friendly experience, and implement the one that best supports clarity and ease of use. #### Background In {T355253}, there has been discussion on how we can handle the 'Other' selection when selecting Event types in the Event Registration form, since: → If we allow Other, we don't want organizers to pick a second event type. If they do, it kind of defeats the purpose of Other. → We want that organizers can pick only 1 option for Other (i.e., Other) but a maximum of 2 options for event types. We have suggestions for that behavior: - Having an 'Other' header with 'Other' as an option (may feel redundant, and unclear). - Separate the 'Other' option with a border, and have a description on the item that mentions the behavior (i.e permitting a single selection only if you select 'Other') - No headers at all + item description - No headers at all (items ordered alphabetically) - When the user selects an event, the 'Other' option is disabled and/or when the user selects 'Other', all of the other event types get disabled. ####Intended audience While organizers (who use Event Registration) are the intended audience for this selection process, we can test on general audiences (i.e., not organizers specifically) since we aim for general usability. #### Acceptance criteria [x] User script is drafted [] At least 5 user testing sessions are conducted using Userlytics as platform [] Observations are collected [] A summary of insights is documented [] A final recommendation is made based on findings, outlining which option should move forward for implementation, and why.