Integrating Github Issues with Pivotal Tracker

Over on we’re using GitHub’s issue tracking as a means for the staff to submit bugs and feature requests. But after years of using Pivotal Tracker, I found GitHub’s issue management to be a little wanting.

Thanks to rich APIs from both GitHub and Pivotal there are many third party integrations written between the two. So many that picking one to use became a task by itself.

After reviewing 5 or so I went with Pivothub, on account of the fact that it was a) recently updated and b) would run in an environment I could set up easily (heroku). I also really like that when a Github-linked story is accepted in Pivotal it’s link on GitHub is closed too.

Since Heroku is a read-only filesystem and I didn’t want to commit my config file to the repository, I forked Pivothub and changed it around to use Heroku’s environmental config variables.

It works pretty well, though some tighter integration wouldn’t be amiss. Right now if a closed issue is repoened via github, it doesn’t come back into Pivotal. The original author isn’t really using Pivotal much these days so any additional features are ones I’ll have to add myself.

Filed under: Software

Tags: , , ,

One thought on “Integrating Github Issues with Pivotal Tracker

  1. If you want to automatically add a “pull-request” label to your stories when a Pull Request is created for it, and automatically mark your story as finished once the Pull Request is merged (removing the label as well), I implemented something to do that 🙂

    It’s hosted on Heroku so you can use it right away for your team.

    Hope you like it!

Leave a Reply

Your email address will not be published. Required fields are marked *