Right now it could take quite a lot of clicks to disable every action related to a plan and all its branches, including branch creation triggers, plan execution triggers, manual runs, and anything else. It would then take an equivalent number of clicks (maybe more) to put things back to how they were later (should I need to do that).

Having a new single-click option would be a time-saver for me and less error prone.

I agree with @Paul Smith.

I just ran into this today. I disabled the plan because a software license that is needed for the build to succeed has lapsed. So we want to temporarily stop running this plan for PR branches. Yet, disabling the plan does not stop it from running when PRs are created.

The entire idea of treating the "master" branch, or any other Git branch, specially in this way is a fundamental design mistake in Bamboo.  Every plan should have an individual plan branch for every branch, including the "master"/"main" branch, and all of them should be treated identically by bamboo: show up as plan branches in the branch list for the plan configuration, be individually manageable, etc.

The only thing that should mark the "master"/"main" branch as special is that the plan could create that initial plan branch automatically when the plan itself is created (or not, either way works fine for me).

There are some scenarios which we only want branch plans to be executed while keeping the master plan disabled.

E.g.

• https://community.atlassian.com/t5/Bamboo-questions/can-i-configure-bamboo-plan-branching-to-exclude-running-a-job/qaq-p/12569
• builds to be limited only the QA branch but not master branch

However, I feel there should be separate options to

• Disable Plan - disable the plan and branch plan completely
• Master Enabled - disable only the master (similar to Branch enabled in the Branch details)