CodeTriage
CodeTriage copied to clipboard
Allow filtering issues
For some projects I am often getting open issues that are in-progress, tracking bugs or other non-fresh issues. It would be really nice if the issues you received were issues that are already un-triaged or ready to be fixed.
I see a couple of things that could be useful here.
- Project defaults: Most projects have a label system and it would be nice to be able to set it once and affect all users.
- User overrides. Maybe a user is only interested in a certain topic. It might be useful to allow the user to override the project default. However since this project is aimed at triage it might not be very useful as there is not much to filter on.
Examples:
- is:open is:issue -label:triaged -label:needinfo no:assignee
- is:open no:assignee
- is:open comments:0
- is:open "created:>2 days ago"
I think this change would really help aim help where it really matters.
Here's things I think would be useful:
- To subscribe to specific labels or restrict specific labels
- Search since last comment time
I rarely see issues with truly zero comments, I don't see the use of searchinf for a specific number or a less or greater than. I could maybe be convinced assignee is an interesting search metric.
I've wanted the ability to search or subscribe via labels for a long time. But it's not a strong want, so i've not implemented it. It's a feature I would consider helping out with though if you're interested in taking a stab.
I see the comment count being not as useful but I think it would be awesome if you could copy a search string from github and use that. I don't know how easy that would be. However supporting common queries and reporting other things being unsupported would be good as well.
Things I would use for sure if they were available:
- Filter on assigned. If I'm triaging I probably don't have to worry if someone is assigned.
- Filter on labels. I think this is an obvious win.
- Filter on last updated time. A triager doesn't need to spend on time on issues that are having an active discussion.
I don't have much time ATM but if no one jumps on this I might try my hand in a month or two.
@kevincox I am not sure how far you went with this, but I decided to give it a try. Have a look and let me know what you think
cc @schneems
I didn't do any more work then shown the in PR. However the discussions didn't go anywhere so I left it unfinished. Thanks for looking into this.