Limit issue assignment to team members only

[Scott Wiltshire]

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.

[Theodora Boudale · Accepted solution]

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:

• https://jira.atlassian.com/browse/BCLOUD-20087

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:

• https://jira.atlassian.com/browse/BCLOUD-12609

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

[Scott Wiltshire]

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.