[Projects Beta] Sort by "last updated", "created" #8518
Replies: 113 comments 68 replies
-
|
Yes please! Specific use case - I want to have a view for "Recently Completed", which would be the "status = done" (custom field), sort by closed date" |
Beta Was this translation helpful? Give feedback.
-
|
I agree! This feature would also be useful to filter out issues that had gone stale and hadn't been updated in a few months. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Agreed! We are working with projects to collaborate between many teams containing a large number of issues, and it would be very useful to sort by 'last created' or 'last updated' to be able to get visibility on the most active issues. |
Beta Was this translation helpful? Give feedback.
-
|
I would love this as well. The ability to filter by last updated in the past week would really be beneficial to see how issues are moving across the team. |
Beta Was this translation helpful? Give feedback.
-
|
i see in the recent changelog |
Beta Was this translation helpful? Give feedback.
-
|
I too am dying for this. I need to order by this badly in descending fashion so recently updated issues bubble to top so I can see what the team is really actively working on discussing. |
Beta Was this translation helpful? Give feedback.
-
|
This would make projects beta much more user friendly for our team :) |
Beta Was this translation helpful? Give feedback.
-
|
This is also our most missed feature. |
Beta Was this translation helpful? Give feedback.
-
|
For us too. |
Beta Was this translation helpful? Give feedback.
-
|
My team needs a view that sorts by the date an issue was closed. |
Beta Was this translation helpful? Give feedback.
-
|
Added +1. Found this feature request after not being able to create a view with "Issues with least interaction" to find out those that maintainers might have missed. |
Beta Was this translation helpful? Give feedback.
-
|
+1 --- need to filter/sort by Created Date & Last Updated Dated |
Beta Was this translation helpful? Give feedback.
-
|
I really need to customize sorting by ticket closing date. |
Beta Was this translation helpful? Give feedback.
-
|
+1 I would love this feature to be added for all of the aforementioned reasons in this long-running thread. :) |
Beta Was this translation helpful? Give feedback.
-
|
+1 What about |
Beta Was this translation helpful? Give feedback.
-
|
That might trim some lists. It doesn't change their sort order, which is EXTREMELY desirable — I daresay, NECESSARY — for managing large, long-running projects with many repositories, and many issues/PRs on each repo. |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 I've been watching this thread for almost two years now, I think it's time to agree that GitHub is not meant nor ready for serious project management :(. On every turn I run into limitations, or lack of simple features that other project management software includes in the MVPs. I think GitHub tried to convert the humble issue into something more robust, but either they do not have the resources, or willingness to pull through. Most serious project management software will integrate nicely with your pull requests so please consider using something else for the sake of your employee sanity ;) |
Beta Was this translation helpful? Give feedback.
-
From what I can see there, that's all in one repository, for which the usual issue/PR management pages (i.e., https://github.com/github/roadmap/issues/ and https://github.com/github/roadmap/pulls/) will work fine. The problems surface when you try to manage a project that includes multiple repositories, which require a merged management, i.e., a PROJECT. |
Beta Was this translation helpful? Give feedback.
-
|
I get the sense they're fairly new to Project/Product Management and Roadmaps. I hope as they mature in that practice themselves, they'll realize the importance and usefulness of all these features we're requesting. I'm hopeful 🍀 There are Atlassian "feature requests" (bugs) that have been unresolved for 5+ years - so I'm keenly interested to see how GitHub steps up to Project Management in the next couple years. |
Beta Was this translation helpful? Give feedback.
-
|
But GitHub Issue Boards are fast and mostly maintenance-free! I value this much more than having a separate team taking care of a JIRA instance. #hiding-in-dark-corner-after-this-comment 😅 |
Beta Was this translation helpful? Give feedback.
-
|
What is more curious, I've been toying with the integration to Notion - as a database of Issues in my repo. |
Beta Was this translation helpful? Give feedback.
-
|
I do appreciate that GitHub boards are fast and simple to use, but that also means they are not feasible for more complex projects. I tried really hard to make them work, but I'm always left with a ton of manual maintenance, label assigning, template maintaining for stories, epics, tasks. Enforcing rules whereas in other software things are just tailored to follow agile/scrum, or linking stories with tasks. Yes Jira has outstanding feature tickets, but not for crucial items like date field sorting and filtering. And yes I'm aware of costs of running a Jira instance, but there are other options out there. My point is: |
Beta Was this translation helpful? Give feedback.
-
|
Can you all please upvote the question instead of adding the same comment over and over? You must know that triggers a notification in every subscribers inbox who is waiting for the really important comment here - that it's working… Just saying - thx 🙏🏼 |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
2024 and absolutely no movement on this key feature is insane... |
Beta Was this translation helpful? Give feedback.
-
|
Does this ask have to be flagged specifically as a feature request or enhancement request somehow to get it on the roadmap? It's got oodles of votes. |
Beta Was this translation helpful? Give feedback.
-
|
I created a couple scripts to ease the pain of this problem. I'm sharing in hopes it will help some others. For context, our contracted software vendor uses GitHub Projects for project management, so all our tickets exist as GitHub Issues. Recently I was asked to comb our backlog to find stale tickets... but without a created at date filter I would've had to check the created date manually... and there were 750 tickets to comb through... I'm sure you feel my pain. The scripts in the linked repo do the following:
Some caveats:
|
Beta Was this translation helpful? Give feedback.
-
|
Why after all this time is there still no ability to sort by basic dates!?!? |
Beta Was this translation helpful? Give feedback.
-
|
This can be done manually... I realize that's not the answer anyone really wants, but it's better than nothing! In Projects, you can add a custom field to a table and make the field type a date. Call the custom field "Reported", or "Completed" or whatever. Then, choose to sort by that field in asc/desc order. If your list is comprised of repo issues, the issues list view for that repo shows when tickets were closed and what not, so it's possible to retro fill these values manually (if you really need to). Going forward, you just have to make it a policy to update those fields when you / your team change the status. It's not all that terrible to manage if you are staying on top of this to ensure the fields are populated. |
Beta Was this translation helpful? Give feedback.
-
|
I agree it's awful this hasn't been provided, and I understand it's not practical for many people to retro fill those, and would be error prone. I'm just offering a "solution" which does exist presently, for those who might be able to make use of it. |
Beta Was this translation helpful? Give feedback.
-
|
That's basically the workaround proposed by @AriEncarnacion a few weeks ago, who also provided scripts to backfill the custom field. Yes, it is an option, and admittedly, it's the first thing that crossed my mind when I hit this roadblock. Ultimately, that's a workaround - we'd be duplicating data which is already available on the issues, it just hasn't been exposed in project interfaces. Hence the ask for a feature request (bug fix?) to correct this oversight. |
Beta Was this translation helpful? Give feedback.
-
|
I'm with you! It's definitely a workaround. And the fact @AriEncarnacion has provided these Python scripts is very appreciated! It sure seems like it ought to be relatively easy to add these date features to GH. I've used a whole slew of commercial Project Management / Repo Management tools for many years. I just now tried these free GH tools for the first time. Right out of the gate I was looking to sort tickets by various dates, and was surprised to not be able to! Hence, I landed here and when I saw this wasn't possible, I figured I'd make the manual/custom suggestion. |
Beta Was this translation helpful? Give feedback.
-
|
Glad the scripts are helping some people! The manual suggestion @BuvinJT suggested is what I would've done if I had started a fresh project. Obviously GitHub is prioritizing other items, but I have a feeling part of the complexity is due to how their DB is setup. Putting those scripts together I had a lot of ??? Moments looking into their GraphQL DB. @ GitHub let me try and make this feature?? 👀 (only half joking...) Hoping this feature gets put on a timeline soon. |
Beta Was this translation helpful? Give feedback.
-
|
Glad the scripts are helping some people! The manual suggestion @BuvinJT suggested is what I would've done if I had started a fresh project. Obviously GitHub is prioritizing other items, but I have a feeling part of the complexity is due to how their DB is setup. Putting those scripts together I had a lot of ??? Moments looking into their GraphQL DB. @ GitHub let me try and make this feature?? 👀 (only half joking...) Hoping this feature gets put on a timeline soon. |
Beta Was this translation helpful? Give feedback.
-
|
If you, like me, have scrolled to here (3+ years into this request) - I know there's not much we can do, but please do remember to upvote. Who knows - maybe some PM at Github is bound to be ticked off at this lack of basic date/time sorting and filtering for their own team, and just get it done. Some year in the far off future, maybe, but still. ¯_(ツ)_/¯ |
Beta Was this translation helpful? Give feedback.
-
|
Did anyone open an official issue with GitHub? |
Beta Was this translation helpful? Give feedback.
-
|
Good callout thanks @Didithekli - I've just submitted a support request, pointing to this discussion for details & community sentiment. |
Beta Was this translation helpful? Give feedback.
-
|
Please fix this!!!! |
Beta Was this translation helpful? Give feedback.
-
The new Projects beta is a fantastic way to consolidate a lot of information but it would be great to be able to have more sort options, such as sorting by the last time an issue was updated, or the date it was created.
Beta Was this translation helpful? Give feedback.
All reactions