Connecting your Basecamp account with BugDigger
You can connect BugDigger with your Basecamp account either signing-in to BugDigger directly via Basecamp or adding Basecamp as a bug tracker associated with your BugDigger account. In both cases you start clicking on Basecamp icon and specifying the name of your instance:
BugDigger integrates with Basecamp account in a manner that doesn’t require that you disclose your Basecamp password to BugDigger. Instead, after you click Next, BugDigger will open a pop-up window and take you to the 37 signals (the company behind Basecamp) for login and authorization.
At this point, depending on your browser’s settings, you may need to allow popup window to open.
After you sign-in, 37 signals will ask you if you want to allow BugDigger to access your Basecamp account.
Click “Yes, I’ll allow access” to enable integration and go back to BugDigger.
At this point BugDigger is enabled to send bug reports to any active project accessible via your Basecamp account.
Notes
If you have more than one 37 signals ID, make sure you’re using the correct one!
If you were signed in to any 37 signals application prior starting authorization for BugDigger, 37 signals’ launchpad will not ask you for credentials and will send you straight to the application authorization page. As the authorization page doesn’t show your current Basecamp identity, you may end up allowing access to the wrong user account. (Here the “wrong” means it’s not the account you intended to use and it has no access to the Basecamp instance URL you gave to BugDigger.)
If BugDigger receives authorization for an account that does not have access to the desired Basecamp instance, it will show an error message. To solve this you need to:
- open https://launchpad.37signals.com and logout from Basecamp, then
- go back to BugDigger and repeat the procedure for connecting with Basecamp.
