-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Change default issues/PRs sort to "Recently updated" #80
Comments
👍 I always sort it by @paulmolluzzo @hkdobrev What do you think? |
I think it's useful for some cases, but not useful for others. Of course it is useful when you to respond to latest activity, but not useful when there's a high-activity open-source repository and you want to try to close new issues and PRs fast and look at some long-running issues/PRs just from time-to-time. Imagine issues with a lot of +1 comments or PRs with a lot of code review comments from others. Whether I'm not sure if this is a commonly shared logic and I'm not even sure having What do you think of having a button which toggles between the two instead of having to click the drop down to the right? |
No strong opinion from me, except that I might get confused by changing the default (I don't know for sure). I don't usually sort issues, tbh. When I'm triaging maybe? |
Adding a toggle button like @hkdobrev suggested would be my second choice. In fact, it's the cognitive strain caused by the Sort drop down that initially motivated this request. I was finding that I'd navigate to a GitHub repository, click Issues, not immediately see the issue I wanted, click Sort and then... ... ... (blink) ... ... try to read the words and figure out which one applied to my case. The one I really need (Recently updated) sits second to the bottom, below options related to comments which sort of look the same. That makes me think that the underlying issue here is that the Sort drop down causes cognitive strain. Too many options without enough differentiation. |
I'll provide a use case that explains why Recently updated comes up the most often. I pick an issue to work on (perhaps because it came in via e-mail), do some coding, send a PR that references it (or perhaps someone else does). That's the issue on my mind (and others I worked on that day). I go to the Issues tab to follow-up on the issues, perhaps to add some additional notes or get information from an ongoing discussion. Where are those issues? No where to be found. Instead, what I see is new issues that came in the meantime that have nothing to do with the activity going on in the project. The projects that this most affects are projects with lots of activity, because new issues are always coming in and occupying the top slots in the Newest sort. |
Despite the obvious stand against options in this extension (which is quite right), this is the feature I feel is most suitable for an option. Of course in best case scenario that would be an option provided by GitHub itself similar to default diff view - split vs unified. When you choose a sort view, this could be persisted until you change it. So I have 2 suggestions without adding options to the extension:
|
Persisted sort definitely sounds intriguing. |
Just wanted to say I've tried this a couple of weeks ago and it isn't easy. Initially I thought I could fiddle directly with the URL - nope, GitHub changes the URLs in a few ways and also there are multiple URLs with the same search (e.g. That said I just wanted to warn people who think about taking this, I'll be willing to assist when possible. However I think it'd be more useful to contact the GitHub team about it and say "please" 😄 |
Definitively something I'm also looking for. |
I would also be interested. While it's not implemented, if anybody knows a workaround (some browser extension that can tweak html, for example), please share here. My desired behavior would be to change the tabs saying "Issues" and "Pull Requests" to a different URL (to specify my sorting preference). Thanks. |
yes, recently updated is the way to go |
Google Code allowed to change the default via the settings tab. I think the best option is to maintain backward compatibility by keeping the current sorting order, but give administrators the ability to change it via the settings tab. |
Especially for milestones, this would be awesome. Milestones are currently sorted on "recently updated", while "closest due date" is more useful in my opinion. |
What's the decision on this? I went ahead and implemented it as a simple change: default the tab to Recently Updated in #454
I'd hate to find the issues in whatever weird order I checked the previous time. It should always be the same
The problem with touching the (issues/PRs) search is that you're gonna have to intercept XHR calls and/or visually change the search field under the user's eyes.
One click vs two clicks. Perhaps it isn't enough of a time saver at that point. |
@sindresorhus Open to make it an option? It looks like many are interested in this. |
@bfred-it Can't we just make it the default? |
I would. Ask @hkdobrev and @jgierer12: #454 (comment) |
I would be in favor if the search field were to remember the search options/filters. Or, alternatively, there could be a user-defined default search filter. That would solve the sort-problem en passant. |
Please simply add a user defined option in settings for sort order. That's it. |
Is that already in the released version? |
Not yet, it hasn't been implemented. |
Looking forward to it, that will be super useful! |
Is that feature already deployed? |
Yes |
And it's a game changer! |
I just installed this extension recently and can't say how annoyed I am with this feature. Is there a way to turn it off? |
@bsarrazin Yes, by opening the extension settings and pasting |
@jgierer12 thank you sir! 🌮 |
As of today, it is sort-conversations-by-update-time: |
Thank you @koppor |
Can we also get an option to put milestones without a due date at the bottom instead of the top? |
The Newest sort option in the issue tracker is rarely useful and not at all what I expect as the default sort. I want to see where the activity is. That's likely what needs my attention most. An update to an old issue and the addition of a new issue should have the same weight. Otherwise, old issues with recent activity stay buried.
I propose modifying the URL of the main Issues tab so the issues are sorted by Recently updated (in descending order) instead of Newest. That can be accomplished by adding the following query string:
The text was updated successfully, but these errors were encountered: