Plan before the Project...?

[Jeremy Roelfs]

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...

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

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]

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