Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Question Details section open by default #377

Closed
LeoMcA opened this issue Apr 20, 2020 · 3 comments
Closed

Make Question Details section open by default #377

LeoMcA opened this issue Apr 20, 2020 · 3 comments
Assignees

Comments

@LeoMcA
Copy link

LeoMcA commented Apr 20, 2020

bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1630499

@jess-cook03 thoughts on this?

@LeoMcA LeoMcA added the review? label Apr 20, 2020
@LeoMcA LeoMcA added this to Triage in SUMO Engineering Board via automation Apr 20, 2020
@LeoMcA LeoMcA added this to the Responsive Redesign V2 milestone Apr 20, 2020
@jess-cook03
Copy link

jess-cook03 commented Apr 21, 2020

@LeoMcA
I appreciate this feedback from a contributor's perspective, but I don't necessarily think that preference alone is enough of a reason to revert to the previous way these details were exposed before.

I can see the point mentioned where if this information is the top priority for contributors and they are looking for that first above all else then yes, we can adjust some of the UI/functionality on that sidebar.

The rationale for allowing users to open and close that info was for simplicity sake and informational organization to best utilize the real-estate in the sidebar. It now has its own defined content space, and depending on the use case the details can be unpredictably long, you could have a lot of details there, so if it was exposed it would clutter the sidebar. We wanted to create more space for the relevant/related content to appear.

I'd like to know how many contributors feel that this information is top priority and if they feel they need to have it exposed or not?

@jess-cook03 jess-cook03 self-assigned this Apr 21, 2020
@jess-cook03 jess-cook03 moved this from Triage to Backlog in SUMO Engineering Board Apr 22, 2020
@jess-cook03
Copy link

jess-cook03 commented Apr 22, 2020

Parking this in the backlog for now.

Per comment above @madasan .... the design intent holds true for keeping it as is, accommodating both public browsing user as well as the contributor.

We can potentially investigate further to see how many community members are effected by this (ie not just a preference of a few).

Maybe make preferences for contributors who are signed up/registered as volunteers... do we attach this kind of view based preference to those users settings?

@akatsoulas akatsoulas moved this from Next Items to Backlog in SUMO Engineering Board May 29, 2020
@jess-cook03 jess-cook03 removed this from Backlog in SUMO Engineering Board May 29, 2020
@jess-cook03 jess-cook03 added this to Design Backlog in SUMO PM & Design Board May 29, 2020
@akatsoulas akatsoulas removed this from the Responsive Redesign V2 milestone Sep 16, 2020
@jess-cook03
Copy link

Closing this as it doesn't seem to have enough grounds to change... seems like a preference this one user had.... no issues have come up around this since.

@jess-cook03 jess-cook03 moved this from Design Backlog to Ready for Review/Dev in SUMO PM & Design Board Nov 19, 2020
@jess-cook03 jess-cook03 moved this from Ready for Review/Dev to Done in SUMO PM & Design Board Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

4 participants