Hello,
we need this fix also in the LTS version of Jenkins. What do I have to do, to get this fix?

Is it possible to use other plugins to workaround this problem?

There is no fix yet, so no chance to get it into the LTS release. The fix above (https://github.com/jenkinsci/jenkins/pull/3277) has been reverted since several old plugins rely on the old and broken prototype functionality. Since we have no UI tests for them (and no responsible UI architect in core) I doubt that we ever get rid of this library.

Ulli Hafner If you see "obat", that's Indonesian spam/a spammer. It's OK if they just create issues, but the vandalism elsewhere disrupts more

It is possible to restore the original / native implementation of an overridden prototype function. It would also be possible to restore whole prototype. Here is an example for a single function. I'm sure you know how to restore whole prototype based on this.

function getNativeFunction(clazz, func) {
    const frame = document.createElement('iframe');
    frame.style.display = 'none';
    document.body.appendChild(frame);
    const nativeClazz = frame.contentWindow[clazz];
    frame.parentNode.removeChild(frame);
    return nativeClazz.prototype[func];
}

if (Array.prototype.filter.toString().indexOf('[native code]') === -1) {
    Array.prototype.filter = getNativeFunction('Array', 'filter');
}

I think that we will never get a sufficient test coverage before making this change. Since I found workarounds for my JS libraries I think we can close this issue.