Feedbacker review

[marleighnorton]

Got a chance to sit down with feedbacker. It’s pretty good! Found a bug I created a ticket for, but otherwise everything’s pretty minor.

• Good job putting everything on one page! One of the issues with multi-page surveys is it's not always clear what questions are coming up, which is irritating.
• Anonymous option needs to be clearer.
• • Radio button list with user's name as the first option, Anonymous as the second, user checked by default.
• • Reinforcing that with relabeling the submit button with "Submit as Marleigh Norton" or "Submit as Anonymous" would also be a nice touch
• Having a way to go through the events with fewer clicks would be nice.
• • Maybe a button at the top of that section which pulls the first event up in a modal and lets you next through the rest?
• • Or let the person do the basic rating from the main page, then click in if they want to add more data
• Adding an explicit Didn't attend option for events might be handy. Possibly that's what the trash cans are supposed to be about, but that seems less obvious to me.
• Reopen Response is not the smoothest word choice. Is there a reason we're holding an open/close state, rather than just having an Update Response button?

[dkapell]

Thanks. I do have multi-page surveys as a later feature add, but it is likely not worth it.

Anonymous - sure, I can try some other designs, including adding it to the submit button

Going through the events - makes sense, I can maybe do a 'save' and 'save and show next' buttons.
The trash is for didn't attend / don't want to give feedback / remove from the list, so i can improve the text tooltip for that, or add text to the form somewhere.

The reason we have submit/reopen is that the con staff / gms only get to see surveys that have been submitted, so I wanted that to be a very explict action. I suppose it might be possible to change things to allow updating a submitted survey, but i don't want anyone to be caught by not realizing that we can see the update immedatly. (also submitting pushes the survey to the end of the survey list, so we can see that it's been updated easier, but there's other workarounds for that)

[dkapell]

I've pushed changes for:

Adding name/anonymous to the submit button. I'm going back and forth about the radio buttons, as I don't want to make the page any longer if I can help it, but side-by-side radios are less clear, IMO (when there's only two options, and they're longer than a numeric rating).
Here's a shot of what it would look like:

I'm not sure that's better than the current switch, maybe with updated text.

Added 'Remove' text to the remove/trash button on wider screens.

I'm working on the other two changes (next event for feedback) and 'update submitted survey'. The other issue with 'update submitted survey is that the way the survey currently works, if you were to update feedback on the survey, it would be automatically updated on the backend and made available, even before you hit the 'update survey response button', because that data is saved when you save in the popup, so by making people re-open the survey to edit those, it's more clear exactly when we see the updated responses. Maybe this is solvable by adding text to the popup when editing feedback on a submitted survey that says that the updated feedback will be immediately available.

[marleighnorton]

Radio buttons: Yeah, that's awkward. If you're really worried about saving space, the correct control is a drop down.

I see what you're saying about the submit button. Maybe leave it as is, due to the backend constraints.

[dkapell]

I'll mock it up with a dropdown, which will actually be larger than the current toggle switch, because of the way i've laid out control labels above fields, if I want it to be consistent with all other items on the page.

…

On Tue, Mar 26, 2024 at 9:11 AM marleighnorton ***@***.***> wrote: Radio buttons: Yeah, that's awkward. If you're really worried about saving space, the correct control is a drop down. I see what you're saying about the submit button. Maybe leave it as is, due to the backend constraints. — Reply to this email directly, view it on GitHub <#12>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABXJFQQNHF73QJP2RYQB63Y2FXXBAVCNFSM6AAAAABFF2XY2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRQGM4TGNZZGY> . You are receiving this because you were assigned.Message ID: ***@***.***>