Bharat Bhatia galtor (I used JIRA's UI, but it downloaded the wrong config.xml I think, sorry Bharat!) thanks for your config.xml. The first thing I did was to open it in a text editor, look at each configuration block, and install each plug-in that you used. I am using Jenkins LTS (version in a comment above), and it selected the current versions of the other plug-ins.
Then I created a Job JENKINS-64962-bharat, saved, and replaced my config.xml. Restarted Jenkins, and reloaded the job configuration. Had a look at the configuration, looked good. Finally, clicked on the button to build with parameters. The Final parameter was blank.
Whenever that happens that first thing I do is check Jenkins logs, and the Scripts pending approval. We use the same security layer (Script Security plugin) as the rest of Jenkins, as well as some Markup formatting, and other security filtering from previous CVE's.

Approving your script, then the parameters were rendered correctly.

Could you confirm if you have the same issue? That was added after we had a security bug reported via the Jenkins Security Team. Depending on the function you have used in your scripts, your Jenkins admin may need to approve it (see script security plugin docs for more).
Bharat Bhatiagaltor (I used JIRA's UI, but it downloaded the wrong config.xml I think, sorry Bharat!) thanks for your config.xml. The first thing I did was to open it in a text editor, look at each configuration block, and install each plug-in that you used. I am using Jenkins LTS (version in a comment above), and it selected the current versions of the other plug-ins.Then I created a Job
JENKINS-64962-bharat, saved, and replaced my config.xml. Restarted Jenkins, and reloaded the job configuration. Had a look at the configuration, looked good. Finally, clicked on the button to build with parameters. The Final parameter was blank.Whenever that happens that first thing I do is check Jenkins logs, and the Scripts pending approval. We use the same security layer (Script Security plugin) as the rest of Jenkins, as well as some Markup formatting, and other security filtering from previous CVE's.
Approving your script, then the parameters were rendered correctly.
Could you confirm if you have the same issue? That was added after we had a security bug reported via the Jenkins Security Team. Depending on the function you have used in your scripts, your Jenkins admin may need to approve it (see script security plugin docs for more).