Feature: job filters

[epechuzal]

Similar to the search box on left where you can type and filter your queues, I'd like a box for job filtering.

Maybe make it fuzzy match e.g. if I type "abc" it will find jobs where ID contains "abc" or name contains "abc" But that is not necessary as long as it is clear what the search will do

Usually if I am moving past like page 2 in the list its because I need a very specific job so a search box would make this easier

[Michael-Gibbons]

Yes I agree, I am currently using this to visualize queues for shopify applications. One application may be installed on many shops but all the shops use the same redis instance. Sometimes I would like to find a job for a particular shop to see why it isn't working as expected, which is difficult to do without a job filter.

I will look into this myself and open a PR if I find a solution.

[Michael-Gibbons]

@felixmosh Not very familiar with this project structure yet (thank you for this wonderful package)

Do you believe this feature is something that could be handled solely by the ui section, or is this something that is going to have to be implemented individually for express, fastify, koa, and hapi?

[felixmosh]

I guess that you will need it at the API level, because there is a pagination, and you don't want to filter the current page only.

ServerAdapters are all working with the api, so there is no need to implement for each server framework.

[PerpetualPhoenix12]

This feature would be incredibly helpful. Currently have 1.4k+ jobs in a queue and if I need to remove just one of them then it becomes an impossible task to do via the UI manually. I have to resort to connecting to the Redis instance to remove the job.

[edumaciel10]

Any news about it?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[abenhamdine]

@stale, stalebot stop doing silly things, it's not because there's no activity the need does not exist any more

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.