Subscribe
Sign in
Fire bot — Let your whole team create GitHub issues via email 🔥✉️️
20
Replies
@keyul: Before we used Fire, for us it used to be tap on the shoulder or send an email to eng team member. Both would be highly disruptive to eng. and inefficient (information lost). Some other issue tracking systems offer the "create issue via email" feature, but not GitHub.
But curious to see what everyone's experience is. How do you do that at Bot Stash @keyul?
@youpdidou As we are a team of two people only, Trello is an easy way to keep track of it. For a bigger team, the use case is similar to you have described.
This is a great idea. At my last Co. we used Github issues and enabling non-technical people to easily submit an issue would have made life easier back then.
Been using this with our team in beta. Loving how it keeps non-github users up to date with comments on the Issue…v slick.
@adcooley Thank you, I’m glad you like it. Always happy to get your questions and feedback :)
Just let us know if there is anything we could do to make Fire better for you!
Dig this. We're a small team, but thinking about trying it out as a light weight support system for some of our clients.
Thank you for hunting us @thinker!
We built the Fire bot to let any member of your team communicate product ideas and suggestions over Email (where non eng. spends most of their time). They can simply email the Fire bot with any suggestions, product fixes or bugs and the issue is immediately translated to GitHub, where your engineering team lives. In return, your engineering team won't have to look at emails anymore, and issues do not get lost in someone's inbox.
To install Fire bot, simply add @fire-bot as a collaborator to a repository in Github, customize your forwarding address, and add your team. Once this is done, anyone at your company can simply start emailing your custom email address to create Github issues.
You can also forward any emails that requires engineering attention (for instance Intercom messages, Sentry alerts, etc) to GitHub using Fire bot. It supports attachments.
We were using Fire internally at first so that non engineering team members didn't have to go to GitHub to create issues. Over time, we found that the bot removed friction, let us collect more feedback, and let eng. almost not have to use email anymore. We just made it available to anyone (and free).
One other use case we've found for Fire – it's where we forward automated alerts (e.g. Sentry, Opbeat, cron, etc). Previously, those alerts would go to some Eng email alias (e.g. dev@, eng@) and could easily get lost. Now, they all end up as GitHub issues which we can easily triage/assign/close.
How about creating github issues within the app itself as in where the test fails?
@mirmayne do you mean running your test scripts for your app and getting GitHub issues created automatically?
@mirmayne Do you use a CI system to run your tests automatically? If so, you can set this up! We use CircleCI and here's my config which creates a GitHub issue whenever I break our main app's build: https://screencast.com/t/zRznt6g...
Product Hunt