We have a very frustrating experience when creating new playbooks. When creating a new Template to run new playbooks, the "Playbook" field is pre-filled with playbooks that were recognized from the Project's source control branch, and completely disregards the Template's source control branch, as specified. Therefore, it is impossible to create a Template based on a Playbook that only exists in a specific source control branch (e.g. in a pull request). Furthermore, trying to bypass the pre-filled Playbook field by typing in our Playbook path directly, which we know existing in that source control branch, does not work as it will revert to one of the prefilled path instantly after clicking away. The system should either pull the source control branch to read the available playbooks, or should absolutely let us type in the Playbook we know exists. Otherwise it means that we MUST merge some version of the playbook to our main/master branch first, for every new playbook we want to create.. which is not only painful but non-sensical.

We are using an Azure Git repo as the source for our project, but per common practice we have a main branch that we fork out into "topic" branches for features, bug fixes, etc. We are using the project option "allow branch override" so we can test without having to create new projects and changing the job template every time we make a bugfix branch. The problem is this: when selecting the playbook for a job template, you can't actually type just anything; it has to be a playbook that exists in the project. If I add a playbook in my bugfix branch that doesn't exist in the main branch, AAP won't let me select that playbook in the job template because (I assume) it's not in the main branch. This happens despite the fact that I'm telling the job template override the branch with my bugfix branch. I have tried a few things but the interface will not budge on this. It keeps either switching back to an old playbook or telling me my playbook isn't valid.