- Issue created by @Rob230
- 🇬🇧United Kingdom ippy
Nice one, thank you for a very simple but useful addition. I stumbled here when checking whether such a feature existed. The patch applied cleanly to * 1.0.0-rc7 (Drupal 9.5.9)
Being able to search through thousands of payloads in order to identify and/or retry or remove the occasional job is really very helpful.
This enables a UI approach that admins can understand and make use of, here to avoid spamming customers who did not attend an event. A (custom) cancel event occasionally fails to fire - leaving notifications remaining in the queue rather than being identified and deleted automatically. Being able to quickly identify these is great.
Overall this seems like a useful and non-controversial addition to the project.
+1 - Status changed to Needs review
over 1 year ago 1:18pm 26 February 2024 - last update
over 1 year ago Composer require failure - 🇵🇹Portugal jcnventura
This is not really a bug, so moving it to the correct category. Also, there is a patch proposed, so the correct status is "Needs review".
And finally, maybe @ippy would like to change the status to "Reviewed & tested by the community", so that this actually has a chance of being committed?
- First commit to issue fork.
- Merge request !26Issue #3406601 by rob230, ippy, jcnventura, it-cru: Expose payload as a views filter → (Open) created by IT-Cru
- 🇩🇪Germany IT-Cru Munich
@jcnventura: I've tested patch #2 from @rob230 with advancedqueue 8.x-1.4 and it worked as expected. Before patch payload field was not available as filter in views. After apply of patch it was available and also useable as exposed filter to search advancedqueue payload of items for user given strings.
I've created a MR against 8.x-1.x which is based on #2 patch without any additional changes.
Moved issue to RVTC.