If I understand it correctly, your active choices parameter returned, when executing your Groovy script, value from another parameter as a String, opposed to an object from the Jenkins code base API. That would be the expected behaviour. The plug-in works by parsing the HTML DOM. So it has access to only objects in the screen (plus the jenkinsProject variable we inject). So in an active choices parameter, the value returned from other parameters would be a string. And then in your Groovy script for that active choices parameter, you would have to query Jenkins in Groovy, retrieving the item/action/etc, and then populate the current active choices element. Hope that helps Bruno |