Simplify project setup in bamboo

In our setup we are using jira/bitbucket and bamboo tightly together.

With bamboo 6.2 work have been done in order to make project setup easier with the new project level in bamboo.. However there are lot of work to do still I think.

In our setup we cannot share, by default, the projects/deployment projects/linked repositories with everyone. (which are the default settings when creating those, and which typically happens if you give the create permissions to everyone). We want the dedicated "support team" to create the "bare" setup then hand it over to the project teams with the correct permissions set so that data are only shared to the team. (If the team later on changes the permission, we can live with that, at least it should be correct from the beginning.

In our setup each project team will have there own dedicated remote agent running on their server, and we don´t have any local agents on the bamboo server itself...

So looking at the setup for bitbucket, the setup is quite straight forward:

The support team creates the project, does some inital settings and hands it over to the team, and the team can create their repositories as they want.

However with bamboo the process gets quite complicated with lots of issues going back and forth between the support team and the project team:

Also if the team later on adds a new repository you would have to go through steps 3,5,6,7 again...

Some suggestions to make the above process more simpler:

1. Add another level of linked repositories. The current one could be changed to global repositories and be kept as it is. Add another level of "project" repositories which by default are only visible if you have project permissions. By doing so, the project teams can create linked repositories by themselves without (by default) sharing it with other teams. If global repositories are needed (eg to be shared between projects, the support could create those.
2. Add another level in deployment project so that you have for example Deployment project -> deployment plan -> environment. By doing so the team can create new deployment plans (without the risk of sharing it to the world), and also the support team can dedicate the remote agent directly to the deployment project.

By doing the above changes, it won´t be nescessary to go through the support team when a new repository is created in bitbucket. The team would be able to create a linked repository themselves, and also add a new deployment plan. (and their dedicated agent would still be able to build and deploy it since its already been assigned to the project/deployment project.)