Hi, I've synced the code, now going through issues. We had quite a fix regressions in the last updates. Looks like both were done to match new requirements in the Jenkins API for plugins (things for security, or improvements in the JS code).
But issues like this one, without a simple step by step set of instructions to reproduce go down into the backlog. If others want it fixed sooner, it'd be easier if 1) someone provided a pull request for review or 2) someone provided a step by step (ELI5, is OK) or a config.xml of the job configuration (screenshots help, thanks, but I'd still need to spend time thinking how to reproduce, if I didn't miss something, etc., whereas with other issues that include better instructions I can just start working on the issue much faster).
A third option is that I noticed there seems to be some duplicated issues, so maybe somebody else reported the same problem in another issue but with the steps to reproduce it, in which case this could get fixed there, but we'd still need someone to test & confirm it.
Cheers
Any observations on this?