Integrate the token-macro plugin  to allow a more dynamic configuration.
At least in the fields "parameters" and "Remote Job Name" one should be able to use tokens.
Yeah, this makes a lot of sense.
To be honest, I thought you got this "for free" with Jenkins since I have done similar stuff with other plugins. Didn't realize they were using the "token macro" plugin.
Regarding functionality, because 'trigger tokens' are directly tied to jobs, would it make sense to just have everything be tokenized, or does that sound unnecessary?
In my experience from other plugins, users will ask for token support on most of the fields, therefore 'yes' I would support it on all these fields.
After all, it does not harm the system if you do support it, but gives users more flexibility
Submitted a pull request for this feature.
PR has been merged.
This will be part of the upcoming release
Version 2.0 has been released.
This will be available during the next Update Center refresh cycle.