jenkinsci / jenkinsci/parameterized-trigger-plugin

[JENKINS-42723] Fix form fields for active choices parameters when triggering builds via the parameterized trigger plugin

Open
#712 2 comments 0 reactions 0 assignees View on GitHub
component:active-choices-plugin component:parameterized-trigger-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
77
Forks
174
Avg merge
22h 27m
Merged PRs (30d)
1

Description

I recently discovered that jobs which contain parameter types supported by the Active Choices plugin don't get rendered correctly when using the parameterized trigger plugin.

More specifically, when accessing the /parambuild/ URL for a particular job form elements provided by Active Choices parameters are rendered as plain-text parameters instead of their correct types. For example, choice parameters with drop down lists appear as text entry fields with no drop-down list at all.

---
Originally reported by leedega, imported from: Fix form fields for active choices parameters when triggering builds via the parameterized trigger plugin


  • assignee: kinow
  • status: Open
  • priority: Major
  • component(s): active-choices-plugin, parameterized-trigger-plugin
  • resolution: Unresolved
  • votes: 4
  • watchers: 6
  • imported: 2025-12-07

Raw content of original issue

I recently discovered that jobs which contain parameter types supported by the Active Choices plugin don't get rendered correctly when using the parameterized trigger plugin.

More specifically, when accessing the <JOB_URL>/parambuild/ URL for a particular job form elements provided by Active Choices parameters are rendered as plain-text parameters instead of their correct types. For example, choice parameters with drop down lists appear as text entry fields with no drop-down list at all.

6 attachments

- [Proper.png](https://issues.jenkins.io/secure/attachment/47524/Proper.png)
> ![Proper.png](https://issues.jenkins.io/secure/attachment/47524/Proper.png)
- [Screen Shot 2017-03-13 at 1.53.47 PM.png](https://issues.jenkins.io/secure/attachment/36427/Screen%20Shot%202017-03-13%20at%201.53.47%20PM.png)
> ![Screen Shot 2017-03-13 at 1.53.47 PM.png](https://issues.jenkins.io/secure/attachment/36427/Screen%20Shot%202017-03-13%20at%201.53.47%20PM.png)
- [Screen Shot 2017-03-13 at 1.54.09 PM.png](https://issues.jenkins.io/secure/attachment/36428/Screen%20Shot%202017-03-13%20at%201.54.09%20PM.png)
> ![Screen Shot 2017-03-13 at 1.54.09 PM.png](https://issues.jenkins.io/secure/attachment/36428/Screen%20Shot%202017-03-13%20at%201.54.09%20PM.png)
- [Screen Shot 2017-03-13 at 1.54.36 PM.png](https://issues.jenkins.io/secure/attachment/36429/Screen%20Shot%202017-03-13%20at%201.54.36%20PM.png)
> ![Screen Shot 2017-03-13 at 1.54.36 PM.png](https://issues.jenkins.io/secure/attachment/36429/Screen%20Shot%202017-03-13%20at%201.54.36%20PM.png)
- [Test_ad_hoc.png](https://issues.jenkins.io/secure/attachment/47523/Test_ad_hoc.png)
> ![Test_ad_hoc.png](https://issues.jenkins.io/secure/attachment/47523/Test_ad_hoc.png)
- [Test_ad_hoc.png](https://issues.jenkins.io/secure/attachment/47521/Test_ad_hoc.png)
> ![Test_ad_hoc.png](https://issues.jenkins.io/secure/attachment/47521/Test_ad_hoc.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.