Pivotal Tracker does one thing: It Rocks. Last year when Morgan introduced me to this agile project management system, I was blown away. It’s a testament to the philosophy of “Do one single thing, and do it really freakin’ well.”
Now, they’ve gotten better with the release of version 3 of their API:
This Pivotal Tracker update allows you to see GitHub or other SCM commits in your stories, your project activity in your team’s Campfire chat room, and introduces the first wave of integrations with other bug/issue tracking applications including JIRA, Lighthouse, and Satisfaction.
This update allows me to add a post-commit hook to my Github account by going to the Profile Page on Pivotal Tracker and creating a new API token, then going to the service hooks page of my Github Repository and adding the following line:
https://www.pivotaltracker.com/services/v3/github_commits?token=PIVOTAL_API_TOKEN
as a post-commit URL.
Now, say I have a story for my recent small Ruby on Rails secret learning project, and that story is #2288984. I can create a commit messages like so:
Ullr:tweetscore john$ git commit -a -m "[#2289377] Add profile/login links back to main navigation"
And that story will be started. I can finish a story by committing with the message:
Ullr:tweetscore john$ git commit -a -m "[Fixes #2289377] Add profile/login links back to main navigation"
The great thing about this, is that if you send “fixes” on a story that’s not started, it will start and finish it.h
I haven’t yet played with Get Satisfaction connectivity yet, and don’t use Campfire or Lighthouse, but this is enough to excite me. It makes a killer workflow.
Now, if only someone would create a Quicksilver plugin for Pivotal Tracker…
[...] the PivotalTracker team actually uses RubyMine. Furthermore, PivotalTracker’s new API has great integration with GitHub’s service hooks. Telling me that surely this problem has been bumped into [...]
hahaha, i would do it if someone creates a ruby plugin host for quicksilver