-
Notifications
You must be signed in to change notification settings - Fork 68
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
Allow users more flexibility in filtering/sorting issues #2
Comments
Hey, I think a filter should be added so that the repositories with issues closed already, are not shown in results. |
Hi, the issues that are searched are supposed to be open. This is done
using the GraphQL API. However, these issues are searched on Github twice a
day, so the issue might be closed after retrieving the searched issues.
…On Thu, 1 Oct 2020, 11:28 Shristi Singh, ***@***.***> wrote:
Hey, I think a filter should be added so that the repositories with issues
closed already, are not shown in results.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACLYAWPNXM7PS2N3FUBLNILSIPZO7ANCNFSM4RZBX3MQ>
.
|
Got it. Would an increased frequency of checks be a bother in any way? Thanks for quick response. (I would try to fix current issue and get back soon.) |
It would also be good to provide a sorting option by stars. Happy to create a separate issue if that helps in tracking. |
Hey, I'm not sure this suggestiong falls under this issue. But... A filter by language would be nice if that's possible. I find a lot of issues most of the time, get excited, only to relise that it's in a language I don't understand 😞 |
Currently, there is only the option to filter the list of issues based on Programming Language, Repository and Type of Issue. User should be allowed to filter issues based on the title, and also sort issues based on things like number of assignees.
The text was updated successfully, but these errors were encountered: