Environment fails to download artifact from a stage when release is being promoted

Issue Summary

When using more than one stage, with jobs creating artifacts, and environments being triggered by those stages, the release will fail.

Steps to Reproduce

1. Create a plan with two stages.
2. In each stage, have a job that generates one artifact. Let's call these:
   1. StageA -> JobA -> ArtifactA
   2. StageB -> JobB -> ArtifactB
3. Create a Deployment project with two environments. Each environment will have a trigger after a successful stage, and will download each artifact. Looking like this:
   1. EnvironmentA -> Triggered by StageA -> Downloading ArtifactA
   2. EnvironmentB -> Triggered by StageB -> Downloading ArtifactB

Finally, run the plan.

Expected Results

Both environments will be deployed.

Actual Results

The second environment will fail to deploy. In the deployment log we will see

Unable to download artifact Non required shared artifact: [ArtifactB], pattern: [artifactB.txt]

In the server logs you will see:

[AbstractArtifactManager] Unable to retrieve artifact ArtifactB for PR-PL7-11 via com.atlassian.bamboo.build.artifact.ServerLocalArtifactHandler@140386c6 No matching Artifact found.

Workaround

Manually deploy EnvironmentB again, creating a new release.