Our developers make heavy use of the WIP and Private flags for their Changes. Currently, the plugin finds and attempts to build these changes a bit too eagerly.

Some configurability in the scanned and filtered changes would be extremely useful. For this use case, a simple control for the search query being used would be sufficient, e.g. we could use status:open -is:wip -is:private.

Controlling the query would also be immediately extensible to more granular workflows, e.g. using a user-set "ready-for-test" review label as a gate on the Jenkins jobs.