You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I don't see a way of adding a sub-group within a group in Bitbucket. I do see a lot of conversation around "stash" (apparently something different from `git stash`?) and LDAP/external user management, but not quite addressing what I'm looking for.
I have several sub-teams within my teams that should all have a shared set of repos they can read from but different repos they should be able to write to. Is there a way I can set up my Bitbucket groups to mimic my organisational setup? Or do I need to set up one group per specific access set?
I was able to set up nested groups in GitHub, so just trying to figure out if I can do the same here.
Hey @Walter Davies
Stash was the previous name of Bitbucket on-premise ( https://confluence.atlassian.com/bitbucketserver/bitbucket-rebrand-faq-779298912.html#BitbucketrebrandFAQ-WhydidwerebrandStashtoBitbucketServer? )
As for Bitbucket Cloud, I don't believe the Cloud products currently support group nesting. We currently heavily leverage nested groups in our on-prem environment and it's a major downside of the Cloud model. There are some other mentions on this topic about Atlassian Access (including from Atlassians) on https://community.atlassian.com/t5/Atlassian-Access-questions/Does-Atlassian-Access-support-nested-groups/qaq-p/1525606 with some extra background and https://jira.atlassian.com/browse/ACCESS-654
Hey @Craig Castle-Mead - you write "We currently heavily leverage nested groups in our on-prem environment" ... we're currently trying to get "Nested Groups" running with our Bitbucket Server 7.21.4 and the Option "Enable Nested Groups" seems to do basically nothing for us. (bitbucket doc ref: https://confluence.atlassian.com/bitbucketserver/connect-to-an-ldap-directory-776640403.html)
Especially, I would have expected the groups to be synced in a "flattened" way as is described for Jira (see: https://confluence.atlassian.com/adminjiraserver/managing-nested-groups-938847047.html)
Can you comment on your Bitbucket on-prem version and settings?