Dan Podsedly's blog



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.

There is also a new version of the API (V3), with support for moving stories, file attachments, as well as activity web hooks. The first version of the API (V1) is no longer available.

Continue reading for more details on what's new.

Dan PodsedlyDan Podsedly
Pivotal Tracker maintenance and upgrades this weekend
edit Posted by Dan Podsedly on Friday January 22, 2010 at 10:28AM

We are planing to do a Tracker upgrade (with new features including API V3 and some integrations) tomorrow, Saturday Jan 23, at 5:30pm PST. We expect the upgrade to take under two hours.

Also, Engine Yard will be performing some maintenance and upgrades our hardware cluster on Sunday, from 10:00am to 1:00pm PST.

Sorry for the inconvenience. If you need access to your project data during the downtime, we recommend you export your project(s) beforehand:

http://www.pivotaltracker.com/help#howcaniexportstoriesfrommyproject

Also, as a reminder, the first version of the API (V1) will be disabled as part of tomorrow's release. More information on that here.

Dan PodsedlyDan Podsedly
tgethr email collaboration and Pivotal Tracker
edit Posted by Dan Podsedly on Friday January 22, 2010 at 09:57AM

If you've been looking for a way to turn emails into Tracker stories, take a look at tgethr. It's an email collaboration service for groups, and it now integrates with Pivotal Tracker.

Read about it in this tgethr blog post.

We're planning a Pivotal Tracker upgrade on Jan 23. As part of this release, we will be introducing a new API version (V3), which will make it easier to follow project activity, allow you to add file attachments, move (re-prioritize) stories, associate source commits with stories, and more.

The current API version (V2) will not change, but V1 will no longer work. If you're still using V1, you will need to change your client code to use V2 or V3.

To find out what's changing in V3, continue reading.