Skip to content
Email -> Sendgrid -> Azure function -> Azure DevOps Bug
C# PowerShell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
EmailBugTracker.Logic
EmailBugTracker.Tests
EmailBugTracker
deploy
images
.editorconfig
.gitignore
EmailBugTracker.sln
Examples.md
LICENSE
Readme.md
Setup.md
azure-pipelines.yml

Readme.md

Email Bugtracker

Email -> Sendgrid -> Azure function -> Azure DevOps Bug

Go to release

EmailBugTracker

Write an email:

email

and have it turn into a bug in Azure DevOps automagically:

bug

Motivation

This project provides an azure function to convert incoming emails into Azure DevOps bugs.

I wrote this

  • because I wanted to use Azure functions
  • to reduce complexity (both setting up and running it) compared to mail2bug
  • as a learning experience for myself

Requirements

To use this requires a valid email domain and a sendgrid account (if you don't have one, Azure provides a suitable free tier). Additionally you need an Azure subscription (this solution costs a few cents per month).

Alternatives

If you are looking for a more feature complete version, look no further than mail2bug. You can even host it on a virtual machine if you have one already.

Alternatively you can also use Flow to achieve a similar system.

How it works

This relies on the Sendgrid Webhooks. Specifically the Inbound Parse feature.

Inbound Parse will route all mails received at the subdomain through sendgrid and also sends them to the azure function.

Based on the configuration the azure function then ignores or processes the emails and creates bugs in Azure DevOps when necessary.

How to deploy

See Setup.md

Examples

See Examples.md

Future ideas

  • Integration for github/gitlab issues
  • Allow different types (feature/workitem) as opposed to only bugs
  • Add email attachments to the created workitem (currently they are dropped)
  • Allow responding to bugs (create comments in the issue)
    • well known senders would also be allowed to issue commands (#close, #assign, etc.)
You can’t perform that action at this time.