Closed jeremiahcurrier closed 9 years ago
Using update many to bulk un-assign may mitigate the issue my spooling up a job rather than you running your own?
On Jan 26, 2015, at 3:27 PM, Jeremiah Currier notifications@github.com wrote:
Intermittently when unassigning many on marking as unavailable some of the tickets will not actually become unassigned.
Option 1. ReWrite 'unassign many' f(x) to be asynchronous - won't totally fix the problem.
Feature Request VS Bug; Bug latter as the user will expect the action to complete 100% of the time.
Note: If the growl notification doesn't go off, the unassign job didn't finish.
— Reply to this email directly or view it on GitHub.
@dpawluk - this is for adding/removing ticket tags - there is no bulk update endpoints for that, just /tickets/{ID}/tags.json
turns out, there actually is a bulk endpoint for this - who'd have known? Solved!
Intermittently when unassigning many on marking as unavailable some of the tickets will not actually become unassigned.
Option 1. ReWrite 'unassign many' f(x) to be asynchronous - won't totally fix the problem.
Feature Request VS Bug; Bug latter as the user will expect the action to complete 100% of the time.
Note: If the growl notification doesn't go off, the unassign job didn't finish.