In normal periods (non-continuous), the "Move awaiting issues to current integration" (link) job, does reset the "ci" label, so all the issues landing to integration are prechecked again.

That's fair enough for our integration purposes, noting that, maybe, it's a bit too late for developer purposes (more about this later).

But, when on continuous periods, that job is disabled and we use to pick manually the issues. In practice, that means that the "ci" label isn't reset ever, so we don't have any recent prechecker resut.

So, this is about to add a new "ci" reset automated job with the following particularities:

• It only will be enabled along continuous periods (to avoid conflicts with the other job) and disabled out from continuous.
• It will work by looking for issues that came to "waiting for integration" status since last execution and having the "ci" label.
• it will reset the ci label, so a precheck will happen on them automatically.
• the last execution time will be annotated.
• Only will run in the public server (disabled as fallback in the laptop one, just in case it's needed).

That's basically the approach. The only point to discuss is the first one and if the "interdependencies" with the other job should lead to disabling it or no and we can keep it running always.