+1

lmao how is this not still implemented, atleast sort by issue number, wth

Its the world's best example right now of Microsoft's inverted priorities. Should they really be iterating on an abandoned, forgotten, unfinished GitHub "Projects" effort when its not A.I. related? The people with money that need a lot more money say, "Nope."

lmao how is this not still implemented, atleast sort by issue number, wth

Its the world's best example right now of Microsoft's inverted priorities. Should they really be iterating on an abandoned, forgotten, unfinished GitHub "Projects" effort when its not A.I. related? The people with money that need a lot more money say, "Nope."

10 years of our life have been stagnated. the hacker movement of 2016 failed when megacorps captured the minds of our best and brightest. the underground lost. we have been waiting for crumbs to fall off the trillion dollar loaf of bread - that never comes.

Adding a custom field that duplicates data in the existing schema and then adding manual step to enter the data so you can then sort... That is not a practical solution. What is being pointed out here is that a fundamental and expected UI feature is missing and needs to be added. Your impractical and somewhat dismissive solution is a part of the reason this feature continues to be MIA.

For the record, this is what I have done, and it's a PITA. I agree with @jeremy-farrance - this should be available by default.

I understand. And while I too would like it to be a default, sometimes you just need to do workarounds. Feel free to dislike my solution. I'll happily continue building software with my team and my own tweaks to GitHub Projects. When it updates for better or worse, I'll adapt.

fttb , a workaround would be to populate the "start date" with the date of the first commit (equivalently for the "target date"), so that we can at least sort by that field..

"workaround" suggests that it delivers what is wanted, which it doesn't. It also requires a lot of manual effort, as I understand things. For me, this is a non-starter.

Wouldn't that be more work - creating a field and populating it based on an event that doesn't happen for every issue?
We're just asking for existing metadata, which already exists explicitly on the issue, to be exposed in the project interface.
Even simpler metadata than parent or subissue progress, which are available in the interface, and probably take a few hoops to present usefully.

@TallTed for me it delivers what I need, some sort of chronological sorting
@aikenka you are right, not all issues have a PR associated -- good point !

While those comments are somewhat encouraging, bluntly, I'll believe it when I see it. 4 years for such a basic feature in a Project view is hideous. It is almost like someone wanted Project views to fail!