IMHO the plan specific permissions should not override the global permissions.

Sorry, this not feasible because -

1. The permissioning requirements could be different for each plan.
2. What you are suggesting would make the "plan specific permissioning" feature redundant - as they (plan specific permissions) get overridden by global permissions.

We do want our developers to create new plans, but we don't want them to bother with the permissions.

Perhaps a better solution would be for Bamboo to read the settings from the Global Permission configuration and suggest the same configuration while creating a new plan?

This way your developers need not worry about what permissions to set and if the need be, you (bamboo-admin) can change the plan specific permission at a later time,

Please let me know what you think?

Regards,
Ajay.

I expect the same behavior across your entire product line.

Thank you for getting back to us.

After much deliberation, we have decided to disable Bamboo (anonymous) access altogether if the global anonymous access permission is disabled.

I have changed the title to reflect this and will update this issue once its scheduled for a fix.

Sorry for the inconvenience.

Regards,
Ajay.