Hi @pentium10
I’ve been working on a feature for my use and wanted to ask whether this is something you’d be open to considering before I submit a PR.
The feature adds “review batches”: jobs from a source tube/state can be moved into an isolated review tube, inspected in the console, and then either returned to the source tube or deleted. Every action is stored in a downloadable audit file.
The intended use case is safely reviewing large numbers of buried/delayed (and even ready) jobs all at once without leaving them exposed to normal workers while the review is happening. A new dedicated paged interface lets you see the selected jobs, including job data, before deciding to delete or return some/all to the original queue.
I realize this is a fairly large feature, so before polishing it for a possible contribution, I wanted to ask first whether you’d be willing to entertain a PR. I’m happy to adjust the scope or implementation approach if I can towards a direction you’d prefer.
This is what it looks like:
Hi @pentium10
I’ve been working on a feature for my use and wanted to ask whether this is something you’d be open to considering before I submit a PR.
The feature adds “review batches”: jobs from a source tube/state can be moved into an isolated review tube, inspected in the console, and then either returned to the source tube or deleted. Every action is stored in a downloadable audit file.
The intended use case is safely reviewing large numbers of buried/delayed (and even ready) jobs all at once without leaving them exposed to normal workers while the review is happening. A new dedicated paged interface lets you see the selected jobs, including job data, before deciding to delete or return some/all to the original queue.
I realize this is a fairly large feature, so before polishing it for a possible contribution, I wanted to ask first whether you’d be willing to entertain a PR. I’m happy to adjust the scope or implementation approach if I can towards a direction you’d prefer.
This is what it looks like: