Bitbucket
Bitbucket email integration
A bug report that arrives by email can go straight into Bitbucket. Forward it to ForwardThis and it becomes an issue on the repo from your instructions, with the attachment on it.
Setup in 30 seconds.
How it works
Connect Bitbucket
Create a free account and connect Bitbucket. It takes about 30 seconds, and you only do it once.
Forward an email
Forward any email to your ForwardThis address along with your instructions. One email can ask for several things at once.
Done.
ForwardThis replies when it's done, with a short summary and links to what it made. Bitbucket has no way to take these back, so anything that cannot be reversed is shown to you first.
Just forward it
to do@forwardthis.io
Fwd: Booking form rejects UK postcodes with a space
File this as an issue in stanfordlane/booking-web, mark it a bug, and comment on issue 88 to say it's the same postcode problem.
---------- Forwarded message ----------
Two people phoned this morning saying the booking form won't accept their postcode. Both had a space in the middle. It works if they type it without one.
Filed stanfordlane/booking-web #94
Booking form rejects UK postcodes with a space · bug
Commented on issue #88
Same postcode validation problem, now tracked in #94
ForwardThis checks with you before it opens or comments. It cannot be undone afterwards.
Some other examples
- “Mark issue 88 in stanfordlane/booking-web as resolved and say it's a duplicate.”
- “Which issues in stanfordlane/booking-web are still open?”
- “What pull requests are open on stanfordlane/api at the moment?”
Everything ForwardThis can do in Bitbucket
Look up tasks
Find issues in a repo
Read a record
Read an issue or pull request in full
Create task
File an issue
Update task
Edit an issue
Attach file
Attach a file to an issue
Add note
Comment on an issue or pull request
Add CRM record
Open a pull request
Look up records
List pull requests
Find pages
List repos
Try it with a real email.
Forward any email to the address below to see what ForwardThis can do. No signup required.
Occasional product emails may follow.
Why you need ForwardThis
Email is messy, every message asking for something different. It means constantly leaving your inbox and juggling tabs. ForwardThis skips all of that: forward an email along with some simple instructions, and it’s handled. Compatible with every email provider, and it works across the apps you’re already using.
Questions
- How do I send an email to Bitbucket?
- Forward the email to your ForwardThis address with a simple instruction, like "file this as a bug in stanfordlane/booking-web". It writes the issue from the email and shows you the repository, the title and the description first. Say yes and it files it and replies with the number and the link. The first time, you'll need a free account with Bitbucket connected, which takes about 30 seconds, and that's the entire Bitbucket email integration.
- Can I turn a customer email into a Bitbucket issue?
- Yes, and that is the main thing people do here. The bug report someone sent you becomes a real issue in a named repository, with its kind and priority set from your instructions. You can also change an existing issue afterwards, moving it to open, resolved or closed, or handing it to someone, and you can comment on an issue or a pull request by number.
- What if I only half remember the repository name?
- Write what you know. Repository names are matched against the ones your Bitbucket connection can actually see, so "the booking repo" comes back with the real candidates and asks which you meant rather than guessing. It can also just list the repositories across your workspaces when you want to look.
- Is there an undo if it files the wrong thing?
- No, and that's exactly why it asks first. An issue on a busy repository is read within minutes and the notifications have already gone out, so closing it afterwards is not the same as undoing it. Everything it does in Bitbucket is shown to you naming the real repository and the real issue, and you can stop it there. It never merges a pull request, and it never touches branches, pipelines or permissions.
- How is this different from Bitbucket's own tools or Zapier?
- Bitbucket is where the work gets done and it's the right place to triage a backlog. Zapier suits a support form that always arrives in the same shape and always becomes the same kind of ticket. ForwardThis is for the email that doesn't fit a shape: a customer describing a fault in their own words, forwarded with a simple instruction saying which repository it belongs in.