There is no change that has occurred as the promotion is its own job, and
therefore has its own ${JOB_NAME}
which is parent_jobname/promotions/< promotion_name>
So the behaviour is consistent when using the custom workspace option.
If you read the wiki page [1] for the plugin there is a warning
We use the promoted builds plugin, and I've just discovered an annoying
difference in behaviour depending on whether a custom workspace is used.
Previously, I used a custom workspace: ${JENKINS_WORKSPACE_PARENT}/${JOB_NAME}
When a promotion ran, the working directory was set to
${JENKINS_WORKSPA
