Make it easier for users to select multiple jobs/actions when submitting run request

[tomodwyer]

This came from a Bristol/Cambridge meeting and Simon's summary here.

The longer-term fixes are in an initiative (improve project.yaml) but it would be good to discuss as a team if there is a quick fix that might be worth doing in the meantime.

From Simon's summary:
"selecting all the actions to run is very slow and unpleasant. This is a known issue.
quickfix proposal: select actions to run via glob: #1652"

[ghickman]

Could we add a way to live filter the actions displayed on the page? I'm thinking an input box which fuzzy searches on action name, essentially what List.js does although I'm not suggesting we use that library. The removal of actions would be a purely visual change so submitting the page wouldn't be affected by a search.

[bloodearnest]

yeah, fuzzy/prefix match and "add to job request" kinda of flow makes sense.

Also, allowing grouping or tagging of actions might be a useful way.

[eli-miriam]

We've now seen extra use cases for this arising from Em's Big Project - if they want to split their pipeline up into multiple job requests, they need to be able to somewhat programmatically select only the DB jobs, only certain subsequent analysis jobs, etc. In general, this would allow researchers to have faster feedback loops w.r.t. running jobs on the secure backend, given that they could more easily/programmatically select only parts of their pipeline.

[lucyb]

This thread provides an insight into some of the workarounds that are being carried out right now.