Fix: Fixed broken sorting on jobs table#2216
Merged
Merged
Conversation
… handling in jobs table Signed-off-by: joshuaunity <oghenerobojosh01@gmail.com>
nhoening
approved these changes
Jun 3, 2026
nhoening
left a comment
nhoening
left a comment
Member
There was a problem hiding this comment.
I tested this against production (asset 129) and it worked very well!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
In this Pr, the sorting based on "created at" was fixed on the "latest jobs" table found in the asset status page.
Look & Feel
Before:
After:
How to test
make sure the asset has some jobs data, so the table is not empty.
Go to: http://localhost:5000/assets/<asset_id>/status
Further Improvements
None
Related Items
This PR closes: https://github.com/SeitaBV/ems/issues/213
Sign-off