hackforla / food-oasis

Repository for the current redevelopment of the Food Oasis Los Angeles website
https://foodoasis.la
GNU General Public License v2.0
72 stars 51 forks source link

there are many "optional" fields in send correction UI #1279

Closed itserindean closed 2 years ago

itserindean commented 2 years ago

Problem: In the send correction UI on both Desktop & Mobile Sites there are many "optional" fields (Name, Phone, Email). Screen Shot 2022-08-10 at 11 05 04 AM

Step to repro: goto foodoasis.la goto map view by entering an address or using current location Click on "details" for any listing Click "send correction"

Severity 1 - Cosmetic problem only: need not be fixed unless extra time is available on project

Heuristics Violated: 5: Error prevention 8: Aesthetic and minimalist design

Recommendations: Perhaps we don't have to ask the information that we don't need. Or we can make them as required fields.

Action Items

Note: the issue in the heuristics spreadsheet (item no. 31) asks to link this to #1131

This is issue was created from a list of food seeker issues identified by a heuristic evaluation completed by @Gigi P & @ryu-jieun at the end of last year.

itserindean commented 2 years ago

I created this with severity 1, as described in the heuristics spreadsheet but I think the severity should be: 0 = I don’t agree that this is a usability problem at all

I think we want the barrier to submitting corrections to be very low--hence only correction is required, but if the submitter wants to submit more information, submitting it parsed into 3 fields is most useful to us and is not a huge burden tos the user and matches how standard form input works across the internet.

sei1122 commented 2 years ago

The issue is related.
https://github.com/hackforla/food-oasis/issues/1242

We talked to @entrotech and set the requirement to Correction and the rest is optional. As @itserindean mentioned above, we wanted submission to be the minimum possible.

I think we can close this issue.

staceyrebekahscott commented 2 years ago

@GigiUxR I am concurring with @itserindean and @sei1122 that this is not a usability issue and is being handled by the related issue #1242 as Seiko mentions. Marking this issue closed. Please advise if you think this should be reopened and addressed.

staceyrebekahscott commented 2 years ago

Added Impact Sprints 2022 label, as I was considering all Heuristics issues as a priority for the sprints.

GigiUxR commented 2 years ago

@staceyrebekahscott @itserindean @sei1122 I agree with closing the issue.