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

Filter for answered questions too #199

Open
jhonatasrm opened this issue Apr 6, 2024 · 1 comment
Open

Filter for answered questions too #199

jhonatasrm opened this issue Apr 6, 2024 · 1 comment
Labels
Discussion The intent of the Discussion tag is to precisely that Enhancement New feature or request Help Wanted Extra attention is needed P1 We definitely want this. It's a major feature, and it's obvious that it would be useful to everybody UX User Experience

Comments

@jhonatasrm
Copy link
Collaborator

jhonatasrm commented Apr 6, 2024

Summary

Today, we've established the default value of 0 for responses to questions in the filter. I suggest it would be beneficial to introduce configurability regarding the option to search for previously answered questions.

Motivation

Enable the addon user to filter for questions that have already been answered but not marked as solved.

Describe alternatives you've considered

Removing the maximum response parameter from the forum question, however, this would result in an influx of numerous questions, encompassing both answered and unanswered ones, while also eliminating the option for users to select between answered and unanswered queries. I'd appreciate hearing suggestions and alternatives as well.

Additional context

Include an additional option on the following settings screen:

image

@jhonatasrm jhonatasrm added Enhancement New feature or request Help Wanted Extra attention is needed P1 We definitely want this. It's a major feature, and it's obvious that it would be useful to everybody Discussion The intent of the Discussion tag is to precisely that UX User Experience labels Apr 6, 2024
@dannycolin
Copy link
Collaborator

IMO, #130 would probably be closer to what volunteers would expect. The main blocker is the API that doesn't offer a simple way to track this information. We would have to send a request for each questions and compare the update field in the API response.

I think the best solution would be to implement something upstream that let us track this thing of user activity and expose it through the API. Bonus point if we can have a GraphQL API instead of the REST API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion The intent of the Discussion tag is to precisely that Enhancement New feature or request Help Wanted Extra attention is needed P1 We definitely want this. It's a major feature, and it's obvious that it would be useful to everybody UX User Experience
Projects
None yet
Development

No branches or pull requests

3 participants