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