Current Status

We have now shipped Project Permissions to 100% of workspaces across Bitbucket.

https://bitbucket.org/blog/project-permissions-are-available-in-bitbucket

Hi Team,

as a connect app vendor - how can we best count all members of the workspace that currently have 'Collaborator' status?

When the collaborator role is deprecated how do we count active users where the result is the same count as Bitbucket's "Users on plan"?

We used this query in the past: `https://api.bitbucket.org/2.0/workspaces/${workspaceId}/members?q=permission="collaborator"` which worked pretty well.

Thanks for your help @patrick Wolf

To be fair from the blog Patrick does say, "We anticipate rolling out these changes next month." So 31st March then??

"We plan to have it generally available this spring."

AUS spring or US spring?

https://community.atlassian.com/t5/Bitbucket-articles/Taking-Bitbucket-permission-management-to-the-next-level/ba-p/2264892

Is there any update on when this will roll out? It was due late last summer accordingly to the video and now pushed to Q1 2023.

Is the roll out dependant on "Pipelines environment variables at project level"? As that appears to only kicked off before xmas.

Appreciate there has not been many feaatures released since begining of December, but some sort of update would be appreciated, we are waiting for these features for a large scale on premises migration to Cloud.

+1

While waiting for this feature to be released, to mitigate the current administrative pain perhaps you could allow for the selection of entire projects - instead of only multiple repositories one by one - in the group management screen.

I'm talking about the "Workspace settings / User groups" screen, with the "Add repository" button that comes up after selecting a group:

If there was a way to select "Add Project" too, while specifying the permissions I want to grant this group on all its repos, I'd save myself from having to first identify all the current repos in some particular project, and then finding and clicking on each one in the flat pull-down that gets to after "Add repository" is selected. Alternatively, at least group the repos by project in the pull-down.

I understand that there are also some product architecture considerations, but in this case it seems to me it would be just an UI improvement. Like, "automatically select for me all the repos in this one project, then set these same permissions for this group on each one of them". Shouldn't take years for Atlassian to get done, but would save years of aggregated clicking time for their enterprise customers.

Recent milestones:

• Aug 22: six-year anniversary of this ticket.
• Jun 14: one-year anniversary of (the most recent time) this ticket entered the "In Progress" state.

+1

Awesome! Another Atlassian ticket to watch. 

Feels like talking to bots for five years.

Any update on the date this feature will be available?

Patrick:

Could you share a link to the recorded session. I was unable to find it.

Also, Gayatri and I will be presenting an early look at these features at TEAM 22 in a few weeks if anyone wants to speak with us. There should be a recording of the session available after the conference.

d6166b8445b0 Thank you for your comment. The BBC team released project settings a few weeks ago and are actively working on project permissions (scheduled for release in Q2-Q3 2022). We are continuing to work on both these features as we understand how important they are to our customers, especially those thinking of migrating to BBC from BBS. Please let me know if you have any further questions or would like to give us some feedback once you've tried out project settings. 

We are currently Bitbucket Server users and we are looking to migrate to a cloud provider. Bitbucket Cloud was my top choice due to the ability to set permissions and other settings at the project level. After doing my evaluation and learning Bitbucket Cloud doesn't provide that feature, Bitbucket Cloud is no longer my first option. You are now pretty much the same as Git and GitLab from a project permission standpoint. This ticket has been open since 2016 with over 500 votes. You should probably just close the ticket stating this is not a feature you will support.

I feel like permissions would be the main use-case for projects even existing?

Whoot woop!  This is no longer blocked!  🎉   I personally cannot wait for this feature since we have Contractors that I would love to grant write access to a couple of projects, but not all projects.

emanuel.yarborough Thanks for the heads up, I updated the link in the original comment. 

Hi @Ruchi,

Looks like your form is having issues or not allowing users access. I get the following:

Hi all,

Thank you so much for your votes and comments on this suggestion.

I'm a designer on Bitbucket and we are doing further research on this topic and would love to invite you to take part in an upcoming customer research study.

Who we’re interested in talking to:

• Admins on workspaces with 250 members or more

• Admins who manage user permissions in Bitbucket

What’s involved in the research:

• Sessions are 1 hour and conducted over video-conference, so you can participate from anywhere around the globe.

• During the research, we'll start with a general chat to get to know you, then, we’ll have some questions to guide the conversations.

• As a token of our appreciation, you'll receive an e-gift card worth $100 USD within 5 days of completing your session.

f you're interested in taking part, fill out the form here.

If you have any other questions at all, feel free to reply to this message. We look forward to meeting you!

Cheers,

Ruchi

This may be useful to some:

https://github.com/thomashenson/add-bitbucket-group

It's a workaround, but still. Worth noting it used the {{group-privileges }}endpoint from API v1. As mentioned above, there is temporary support for this, so should be OK for the time being.

We have just migrated from a (very) old Stash server to Bitbucket Cloud.

We had to scratch our heads for some time trying to figure out why we didn't understand how to set permissions, only to search and find this request and dozens of other comments about this.

Granular and inheritable permissions are pretty essential for us, and everyone else, to be able to delegate responsibility to the relevant Team Lead or Manager, but currently they would need to be an Administrator on Bitbucket itself, or we host 1000+ Workspaces. Neither of these are suitable solutions.

Looking forward to adequate user and group management being implemented soon.

This project is in active progress now

In my company with 2000+ Bitbucket repositories and absence of centralised management it becomes system/security engineer nightmare to ensure consistent permissions/branching configuration across all repositories which becomes really critical when you use gitflow/gitops way of doing things.

Bitbucket Cloud does not have officially supported terraform module https://jira.atlassian.com/browse/BCLOUD-17209?focusedCommentId=2684875&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2684875  neither project permissions to simplify centralised management.

It looks funny how you promoting DevOps friendly stuff in Jira (kanban, kanplan etc) but ignoring basic principles of config management and Infrastructure as a Code in the Bitbucket. 

Please help us  ! 

I'd like to recognize the extraordinary service of the group-privileges endpoint from API v1. It's still going strong with "Temoporary" (sic) support. Thank you, Atlassian for keeping it running. I've used it dozens of times, though the call is wrapped in a try block with this comment:
 

// Add [REDACTED] group permissions, until April 2019
// https://confluence.atlassian.com/bitbucket/group-privileges-endpoint-296093137.html

The catch block logs a message explaining how to add permissions to the repo in the browser. Thankfully, it hasn't yet been hit. 

I'd remove the whole block if I could set Project permissions.

Do I understand correctly that this is dated 2016 and the team is still working through the technical details? What does this mean for a potential release date? Would this be in this decade? I'm not sure if we could afford to wait that long.

Also, it would be nice to have project level branch permissions as well. It is really frustrating to input branch restrictions for each and every repository I have (more than 100)

What could be the timeline for such a feature like putting settings at a project level?

Project permissions are a priority for Bitbucket. The team is working through the technical details of how to enable permissions and settings at the project level but, at the moment, we are not sure when we will be able to start work. We are, however, actively working on project settings and allowing admin to set settings at the project level. 

I have 216 repos. I don't understand how this could have been forgotted from the server version. 

Also with some plugin like control freak, I was able to put restriction on commit based on the project. Now I need to setup everything for every repos. 

What is the purpose of the project. Only for decoration. It's a shame. 

gitlab has this essential feature. we gave up on bitbucket.

When this feature will reconsider? This is one of the essential needed features.

Agree; this would be very helpful. We're in the process of migrating a number of teams and their hundreds of repos over from GitHub, and having to set the permissions on each repo is really onerous. If we could say that Groups A, B, and C should have default Write access and Groups D and E should have default Admin access to all repos in Project 123, it would be a huge time-saver.

I have 47 repos to manage. Just to add a simple thing like it should include the Jira key in the commit message I need to do it 47 times rather than just 1 time at the project level!

I updated the status of the project above and here is the link to our public roadmap:  https://www.atlassian.com/roadmap/cloud?selectedProduct=bitbucket

It would be great if this team could publish a roadmap.   I am trying to stay with Bitbucket as our company repo, but the lack of features or movement will likely lead to a change if we can't believe that changes are coming.

This would be huge, i think also related is the ability to maybe use regex filters or something like that to automatically assign groups to repos.  Right now the ability to admin within a workspace is very difficult, clearly using project level settings would be ideal.  What is the timeline for this?

Lack of project-level permission heavily affects the usability & maintainability of the whole system. It is obviously not possible to keep track of hundreds of repositories individually and separately.

 I also suggest adding a couple of different project-level adjustments such as branch permissions, configuring default branches, PR settings etc.

This should be a priority action. I have a scenario that I need to put admin user for one project, but as it is, if I become an admin user, it will be admin for all my workspace.

I've mentioned this directly to @pwolf in a previous meeting, but this change is immensely important to our organization. We migrated from Data Center to Bitbucket Cloud and had our permissions managed at the project level. We have maintained this structure, but it is significantly more effort than it should be.

Definitely not up to Enterprise standards. Bitbucket Cloud is still a startup solution.

Its a little shocking this is not built... The sever edition has this functionality. Its extremely important if you work with contractors. You want to provide them the ability to create repos within the project they are hired for; however, to accomplish that you must provide them admin access to your literal entire Bitbucket account... It is literally an all or nothing situation. 

I really can't wrap my head around this. First we have to create all users and groups by hand, and then fix permissions in repo level instead of project? ffs

You would think that this is really basic functionality, and implementing it would have a high priority, especially if you want bigger teams to properly be able to configure and manage the permissions of there repositories in a sensible and manageable way.

This is my first time working with Bitbucket, and I just can't get rid of the feeling of a very immature piece of software, The features it does have are pretty well implemented, but it's missing way too many features and options that Gitlab and GitHub are already offering for years.

Hi all,

Thank you so much for your patience on this suggestion.

I'm a designer on Bitbucket and we are doing further research somewhat related to this topic and would love to invite you to take part in an upcoming customer research study.

Who we’re interested in talking to:

• Users or admins who have recently migrated or considered migrating from Bitbucket Server to Bitbucket Cloud

What’s involved in the research:

• Sessions are 1 hour and conducted over video-conference, so you can participate from anywhere around the globe.

• During the research, we'll start with a general chat to get to know you, then, we’ll have some questions to guide the conversations.

• As a token of our appreciation, you'll receive an e-gift card worth $100 USD within 5 days of completing your session.

If you're interested in taking part, fill out the form here.

If you have any other questions at all, feel free to reply to this message. We look forward to meeting you!

Cheers,

Stephanie

The ideal situation for us would be to create groups for Bitbucket using the Jira Administration and that we can create their workspaces under one roof and one invoice.  Right now I have 9 invoices for all Air Canada Developers in different IT groups.  I should be able to create a group for each IT team and provide them their Bitbucket workspace and have one account for Bitbucket.  We have over 800 members within these Workspaces. 

We actually bought Bitbucket as a piece of cloud software for Mercurial, and Stash was built later separate code base. I wish we had started with an architecture that allowed us to scope permissions across objects, but its very flat right now, so reworking the permissions model ends up being an architecture-level change. Its not about requirements or interaction models, its just about having bandwidth to take this on. Right now, my team is entirely consumed with improving code review, which appears to be a pain point for a lot of customers. 

Jarred, since this is robust and well defined in the server version, what is the holdup?  I feel like Atlassian has started over on the cloud versions rather than migrating the server versions to cloud. Confluence and Bitbucket are missing so many critical features we cannot use the cloud versions of these tools.

Just cleaning up. I'd like to prioritize this work, but it's not scheduled yet. Its really top of mind for me though, I'm aware this is a blocker for larger teams. 

@jarredc is this moving forward or just cleaning-up the backlog? It's a pain in the 4$$ to handle permissions with many repos...

Second that. Not having this feature compicates building of processes in my company (as there are many ingreation depending on that)

I agree with you jainigo. I want to get this into the product and I felt bad about changing the status. I will definitely keep updating the status as we move toward working on it.

Thank you for the update. Anyway it's disappointing that after almost 4 years since this ticket was opened we still don't have a clue about when we will have this functionality. Managing permissions without project permissions is a pain.

Hi, everyone. 

In order to set proper expectations I am moving this from In Progress back to Future Considerations. We are still actively working on it in Design and requirements gathering but have not starting engineering work yet. 

It remains a highly-valued feature by us and our customers.  We want to implement it as soon as we can but we are engaged in a few other high priority areas first:

• Workspaces - which we just announced this week
• Our New Code Review Experience
• Integration with Admin Hub

We will continue to update this page as we make progress and start engineering work.

Thanks,

Patrick

Do you have any update on this?

Also waiting for this feature