Errors in Artifact Download task after changing Build key

Still need help?

The Atlassian Community is here for you.

Ask the community


After moving a Build plan and changing its key, you may see the following errors in the atlassian-bamboo.log when exporting the plan as Specs:

2018-01-10 14:05:51,953 ERROR [http-nio-8443-exec-190] [ViewPlanSpecs] Chain PROJ-PLAN does not exist.
com.atlassian.bamboo.specs.api.exceptions.PropertiesValidationException: Chain PROJ-PLAN does not exist.
	at com.atlassian.bamboo.plugins.artifact.export.ArtifactDownloaderTaskExporter.toSpecsEntity(
	at com.atlassian.bamboo.configuration.external.helpers.TaskDefinitionExportHelper.toSpecsEntity(
	at com.atlassian.bamboo.configuration.external.PlanConfigExportServiceImpl.lambda$null$13(
	at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(


This appears to be caused by the task retaining the old build key in its configuration.


This can be resolved by following the steps below.

Given a Build plan with key PROJ-PLAN, that had been changed to PROJ-MYPLAN

  1. Go to the Plan configuration for PROJ-MYPLAN
  2. Check for any Artifact Download Task
  3. Check the source plan for any references to the name for PROJ-PLAN?
    • If so, please select the new name of PROJ-MYPLAN
  4. Retry the export to Bamboo Specs

Last modified on Jan 11, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.