Sasha Yelkhovenka

It would be great to accept this PR.

I'm surprised this kind of functionality was integrated into sidekiq. I thought you should always break down long jobs into smaller ones if they require sidekiq-iteration. If it was built...

> * Clear all existing jobs from all namespaces The only reason not to do it is that the user can change the job status (enabled/disabled) from the UI and...

> The only reason not to do it is that the user can change the job status (enabled/disabled) from the UI and it should persist between deployments. The job status...

This wasn't fixed, right?

> @freemanoid @zedtux I had the same issue and I fixed removing the Cronjobs in the old namespace, something like this: There are a couple of downsides for this approach:...