How to download an artifact from a parent plan branch no a new plan

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

It is still possible that you may need to download an artifact from another plan, you may even need to get it from a specific plan branch. This article intends to explain how to do it.

Solution

Make sure the dependent or destination plan has a plan branch with the exact same name of the plan branch used in your parent/origin plan.

In other words, this is how the artifact download is handled in each situation:

Let's suppose you have these artifacts in your parent/origin plan:

Plan branch

Artifact name

Artifact content

master

test.txt

test.txt from branch master

branch1

test.txt

test.txt from branch branch1

This will be the result of destination plan:

Plan branch name (destination plan)

Artifact downloaded (from source plan)

Artifact content

Comment

master

test.txt

Content from master

The master will get the artifact from master

branch1

text.txt

Content from branch1

In this case, the branch name matches a plan branch from source plan, so the artifact from plan branch1 will be picket

others

text.txt

Content from master

If there is no plan branch name match so the artifact from default branch will be picket

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.