Github fills in the default issue search (e.g. https://github.com/github/hub/issues) with "is:issue is:open".
As we typically have been using labels to categorize our issues, I would want to be able to customize this default selection of filters for some projects, so when I land / go back to the issue page I get shown the most relevant issues that are assigned to me.
I understand I could bookmark the exact link (e.g. https://github.com/github/hub/issues?utf8=✓&q=is%3Aissue+is%3Aopen+label%3Abug), but I don't find that a good solution as I regularly click on the issues link in Github and it obviously brings me back to the default search filter.
Thanks for this feedback! We're always working to improve GitHub, and we consider every suggestion we receive. I've logged your feature request in our internal feature request list. Though I can't guarantee anything or share a timeline for this, I can tell you that it's been shared with the appropriate teams for consideration.
Please let me know if you have any other questions.
Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!
To add a bit of more detail. We would like to have the default search term which is prefilled to the input field being "is:issue" only. This would make our user search for closed issues as well by default.
I'd also like to add a +1 to this.
For my use case it's not necessary that the default filter option be modifiable, but it would be nice to be able to add custom filters to the dropdown. For example, I'd like to be able to have a way of seeing all PRs that are currently awaiting review from me and require approval.
I suppose once custom filters are implemented it's not hard after that to add a feature to select one of those filters to be the default filter.
In one of our project, we have a lot of feature requests which are not real issues. We'd like to change the default view to show only issues (no feature requests).
What would be nice is to be able to define pre-defined filters which serve as navigation of issues. And ideally, there should be a number associated with each pre-defined filter to show how many issues are in that category.
Tags are insufficient for two reasons:
- we have more than 60 tags
- tags require several clicks to reach