Unassigning issue sets it to Charles Guse (BB-7159)

Issue #5964 duplicate
created an issue

Who is Charles Guse? This person should NOT have access to my Repo.

I unassigned an issue and instead of the Assignee being -- it is some random BitBucket user. This is not good. See screenshot.

There is no Charles Guse on my team.

Comments (3)

  1. Zachary Davis

    Charles Guse does not have access to your repo, and does not actually have your issue assigned to him (check the assignee value in the top right). There's a bug in our issue changelog code that has to do with Charles Guse having the username "none".

  2. Log in to comment