This could be caused by one of three problems.
- First and foremost, you need to make sure that you've connected the desired Bitbucket repository to your corresponding Sifter project. To do this, visit the Project Settings area in Sifter for the desired project and then go to the Integrations page to obtain the project token to provide to Bitbucket.
- You may need to link your Bitbucket profile to your Sifter account. Here's how to link your Bitbucket account. Once that step is complete, we'll be able to recognize your commits and update your issues.
- If you've done steps one and two, the most likely problem is that your local Git configuration isn't set up with one of your recognized email addresses. When you link your Bitbucket profile to Sifter, Sifter receives all of your email addresses that you've associated with Bitbucket. When Sifter receives commits, it uses these email addresses to identify you. So if your local Git config email doesn't match one of these recognized email addresses, we won't know who you are. The best solution is to update your Git config to use one of the recognized email addresses. If, however, you need to use an email address that isn't listed under the recognized email addresses, you may need to unlink and re-link your Bitbucket profile so that Sifter can pick up any new email addresses that you may have added to Bitbucket.
If none of these solutions solve your problem, email our support and we'll get to the bottom of things.