Skip to content
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

Add filtering to the job base table #392

Open
Pasarus opened this issue Nov 29, 2024 · 0 comments
Open

Add filtering to the job base table #392

Pasarus opened this issue Nov 29, 2024 · 0 comments
Assignees

Comments

@Pasarus
Copy link
Member

Pasarus commented Nov 29, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants