Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Plan before the Project...?

Jeremy Roelfs June 12, 2018

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
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 12, 2018

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

Jeremy Roelfs June 13, 2018

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
AUG Leaders

Atlassian Community Events