You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The table can be a bit hard to parse if you want to do something more than just see what runs were last processed.
We should add filtering options for the following:
Fuzzy search for titles
Fuzzy search for filename
Filter out values with N/A for job start/end and run start/end i.e. incomplete data (tick box)
Tick boxes for which instrument to show in the ALL instruments table (People may want a group of instruments)
Ranges for the 4 date types, job start/end and run start/end
Ranges for the experiment numbers
Filter what job types to show (Autoreduction, Simple, Reruns)
Filter job result type (Success, Failure, Not Started etc)
Suggested work pattern:
1st complete a plan for what it looks like then get agreement with the team as this could be a substantial UI change.
2nd Plan what endpoint changes need to occur for the API (likely just adding a bunch of args to endpoints that already exist)
3rd Implement API changes
4th Do the UI changes in the frontend
The text was updated successfully, but these errors were encountered:
The table can be a bit hard to parse if you want to do something more than just see what runs were last processed.
We should add filtering options for the following:
Suggested work pattern:
1st complete a plan for what it looks like then get agreement with the team as this could be a substantial UI change.
2nd Plan what endpoint changes need to occur for the API (likely just adding a bunch of args to endpoints that already exist)
3rd Implement API changes
4th Do the UI changes in the frontend
The text was updated successfully, but these errors were encountered: