Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,022
Community Members
 
Community Events
176
Community Groups

Suggestion to adding a repository permission level, between write and admin

Edited

Bitbucket provides 3 repository permission levels.

  • read
  • write : Cannot edit all repository setting
  • admin : Can edit repository setting (including delete Repo.)

As a developer in team, We have multiple developers working on multiple repositories.

Most developers are granted write permission, and only the leader or a few developers have admin permission.

This is because admin privileges have the right to set the repository itself.

But, coworking in multiple branches in the repository, and settings such as webhook notifications are required for external services( like slack ), or epic branch rule setting, it becomes cumbersome for the admin user to manage everything.

 

So, I suggest to adding a repository permission level, between write and admin. (like maintain level in Github, maintainer in Gitlab)

Aside from dangerous functions like deleting and moving repositories, Is it possible to allow some permissions to be edited?

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events