Jenkins pipeline sections such as parameters, triggers (ex: cron) and there cold be other options other than this, are not reflecting in jenkins job until I trigger the build manually.

This is really frustrating for us because we use jenkins CASC to deploy our changes including jobs. So, every time we deploy a new change, all the parameters and cron triggers gone. Is there a way for jenkins to pull the pipeline file when the job is create or updated, so that we can see parameters and other triggers. Its difficult for us to do manual trigger for 100's of jobs.

For now we have shifted parameters and cron triggers from pipeline file to DSL job.

If there is nothing jenkins can do about this, then its better to provide note on pipeline documentation to mention this issue with pipeline jobs and encourage users to use move these kind of settings from pipeline to jenkins job.