The pull request[1] from wolfs will fix this at the build level, and list them on the build page, for the triggered downstream builds.
And the triggered builds will have started by Upstream cause linking to the correct build.

However the project page will not be able to display these links as the parameters do not exist so cannot be evaluated, which is why there are not shown in the upstream/downstream list.

[1] https://github.com/jenkinsci/parameterized-trigger-plugin/pull/19

I can't apply the pull request to the master. It looks like all the changes are already merged. Is it possible or am I doing it wrong?

I'm cloning the repo with:
git clone https://github.com/jenkinsci/parameterized-trigger-plugin.git

Then applying the patch using (using --whitespace=fix because of whitespace errors):
curl https://github.com/jenkinsci/parameterized-trigger-plugin/pull/19.patch | git am --whitespace=fix

Trying to use the master didn't resolve the issue though.

Seeing as you can clone the master repo,
there is a pre-merged branch available named 2.17-RC

you should be able to swap to use that using

git checkout -b 2.17-RC remotes/origin/2.17-RC

then do a mvn clean install.

Note: this is under testing so make sure you backup any critical jenkins data first and look at the commit log for it to see if any of the other pull requests cause you issues.

Otherwise have you tried following the merge commands in the pull request itself.

create a branch
pull branch from src repo
merge into current branch.

and for pull 19 this is

git checkout -b wolfs-without-deps master
git pull git://github.com/wolfs/parameterized-trigger-plugin.git without-deps

This will then give you a branch with these changes.

and if you then want that branch merged into master

git checkout master
git merge wolfs-without-deps
git push origin master

Thanks!

I've used the RC and it did the trick. When is it expected to be released?

Fixed in 2.17-RC.