I am experiencing a problem with parameterized project names that is related to resolved issue #8969. Github Authorization Settings appears to be incapable of granting enough permissions to allow for parameters in the project name of the copy artifact plugin.

Steps:

In a project, 'B', that is triggered by another project, 'A', create build step "Copy artifacts from another project" where the Project Name property contains a parameter (e.g. $TriggeringProject). In "Configure Global Security", set Authorization to "Github Authorization Settings." Grant READ permissions to everyone.

Build project A. Project B will trigger and fail on the "Copy artifacts" stage with a message:

Unable to find project for artifact copy: {project name}
This may be due to incorrect project name or permission settings; see help for project name in job configuration.

If the Authorization is instead set to "Anyone can do anything", and project A is built, then project B will succeed. If the parameter is removed from the project name, and project A is build, then project B will succeed.