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,457,225
Community Members
 
Community Events
176
Community Groups

Limit issue assignment to team members only

Edited

Our issue list in Bitbucket is public as we want non team members and customers to be able to create bug reports and feature requests. However it's extremely annoying that there seems to be no way to limit the member search when assigning issues to team members only. I have searched everywhere for this and can't find it. It would seem mind boggling to me if such a simple and essential feature wasn't available.

For that matter a \'@Mention should also be able to be limited to the issue reporter and team members but this also doesn't seem possible.

Please tell me I'm wrong and there is a simple way to do this.

1 answer

1 accepted

0 votes
Answer accepted

Hi Scott,

A user with no access to the repo cannot be set as an assignee for an issue. They show up in the user dropdown when you try to select an assignee, but attempting to update an issue with an assignee that does not have repo access will fail with the error "User is not a collaborator on this repository".

I created a bug report about this in our issue tracker:

You can add yourself as a watcher (by selecting the Start watching this issue link in the bug report) if you'd like to get notified via email on updates. You can also select the This affects my team link to indicate you are affected by this issue.

Our development team tracks bugs in that issue tracker and will post an update on that issue when this is fixed. Please note though that we don't provide ETAs and bug fixing is implemented as per our policy here.

We have a feature request to limit mentions in issues to team members only:

The request has been closed as it is unlikely to be worked on in the near future. However, I would suggest adding a comment with your feedback, as our product managers continue to monitor even closed requests.

Kind regards,
Theodora

Thanks for the response Theodora. This is disapointing that the bug exists for so long with no priority to fix as it really makes Bitbucket issue lists practically unusable as the username search  is more or less unusable. It seems Atlassian has a very transparent strategy of "move to Jira" for defects in other products.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events