Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Plan before the Project...?


What came first the chicken or the egg?

I need to start a new project... Why would i be required to provide a plan and artifacts for a Project that has no Plans/Builds... let alone artifacts?

But I'm required to pick a plan from a different project? I don't want artifacts built into my release from a different project... what is that?

This makes absolutely no sense.




EDIT: Use CREATE > New Plan. Then it lets you create a new project, setup your repository, etc...

1 answer

1 accepted

1 vote
Answer accepted

You might also be confusing a build project with deployment project. Plans reside in a build project. You can create a new build project while creating a plan or choose an existing project.

Once the plan is created, create a deployment project and associate it with the build plan.

The hierarchy is:

Build Project -> Build Plans -> Deployment projects -> Deployment Environments

Okay. That makes sense, but the UI doesn't really explain that flow very well. Thanks!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 9.0 is now available

Hey there, Data Center community! I'm Martyna Wojtas and I am the Product Manager for Bamboo Data Center. I’m excited to share that Bamboo 9.0 is now available. We purpose-built this platform to help...

310 views 0 7
Read article

Atlassian Community Events