-
Notifications
You must be signed in to change notification settings - Fork 96
Add Sorting Capability for finished_at and failed_at Fields #246
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
Comments
To be honest, I was a little confused when I opened the failed queue and found it sorted oldest to newest. I would prefer the failed queue to follow the finish queue, showing newest jobs first. Here's my expereince:
|
I agree, I was hoping for a change like #210 to make it easier to get to the recent jobs, but I also feel like changing the default order should be much easier and IMO shouldn't be controversial. Making it sortable would also be great but that's a bigger UI change. It would be consistent with the "Finished Jobs" tab as well. Hmm... might be worth submitting a PR just to change to see if it would be accepted. |
I also found the default sorting by oldest first confusing — I definitely see value in changing it to show the most recent jobs first. I’ll try creating a pull request to sort them in descending order by default! |
Updated the default ordering for job executions to sort by job_id in descending order (job_id: :desc) instead of ascending. This change makes recently finished or failed jobs appear at the top of the list, aligning with expected UX and improving discoverability.This change addresses rails#246.
Feature Request: Sorting by finished_at and failed_at fields
It would be very useful if the mission_control-jobs gem could support sorting jobs not only by their jobed times but also by other relevant timestamps such as finished_at and failed_at.
Example Use Cases:
This would be particularly handy when you want to view jobs that have recently failed.
The text was updated successfully, but these errors were encountered: