Redesigned new job page: CascadeChoiceParameter does not work

[Eyepatch5263]

Fixes #26371

Testing done

I tested both the scenarios with the provided groovy code

1. When ui.flags.new-job-page is false
2. When ui.flags.new-job-page is true

Now, both the results are giving the same UI State

Screenshots (UI changes only)

Before

After

Proposed changelog entries

• human-readable text

Proposed changelog category

When we build a job with the provided groovy code, we will test it with both the scenarios, first with ui.flags.new-job-page=true and ui.flags.new-job-page=false and then build the pipeline both will give us the same UI under the build with parameter section.

/label bug

Proposed upgrade guidelines

N/A

Submitter checklist

• The issue, if it exists, is well-described.
• The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• UI changes do not introduce regressions when enforcing the current default rules of Content Security Policy Plugin. In particular, new or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
• If it would make sense to backport the change to LTS, be a Bug or Improvement, and either the issue or pull request must be labeled as lts-candidate to be considered.

[mawinter69]

This is not solving the problem. You screenshots refers to the old UI but the issue says this happens when you use the new job page.

As already mentioned the problem is in active choice plugin which attaches with DOMContentLoaded but as the things are loaded delayed the event has already fired when the js code is loaded.

[MarkEWaite]

Closing the pull request because it does not resolve the issue and because the pull request template is used incorrectly. If you decide to continue on the related issue, be sure that you place the proposed changelog entry in the section that is labeled for the changelog entry.