If you’re looking for custom reporting and analytics for your projects, Easy Insight just added integration for Pivotal Tracker.
More details about how it works on the Easy Insight site.
We are no longer posting news about Pivotal Tracker here. You can now find all Tracker posts over at www.pivotaltracker.com/community/tracker-blog/
The integration lets you easily pick a Tracker story from within RubyMine and create a task out of it. RubyMine tasks let you organize your work into different contexts. You can switch between tasks, and create source control changes based on them.
To use it, you’ll need a Tracker API token. Go to your My Profile page to get that.
Next, in RubyMine, go to Settings, and add a Pivotal Tracker task server (under Tasks/Servers). Use http://www.pivotaltracker.com for the URL, and enter your API token and Tracker project ID.
Note: This version of RubyMine sometimes hangs when trying to add a task server through the settings UI. As a workaround, you can edit the workspace.xml file, located in the .idea directory under your Rails root. Add the following under the element:
<servers> <PivotalTracker shared="false" url="http://www.pivotaltracker.com"> <option name="APIKey" value="YOUR_API_TOKEN" /> <password /> <option name="projectId" value="YOUR_PROJECT_ID" /> <option name="useHttpAuthentication" value="false" /> <option name="useProxy" value="false" /> <username /> </PivotalTracker> </servers>
Once the task server is configured, you can use the Switch to Task dropdown in the RubyMine tool bar to add a new task based on story in your Tracker project, or change between existing tasks.
You can optionally create a source control change based on the task, allowing you to preserve the story context all the way through to the commit.
If you’ve using Tracker’s post commit hook to automatically link commits to your stories, you can reformat the change description to match what Tracker expects (e.g. [completes #123456]) before you commit the change.
A common feature request from teams that have multiple projects on the go in Pivotal Tracker is the ability to move stories between projects. We’ve just added that feature.
To move a story, or a group of stories, select them first, using the selection check boxes to the right of story titles:
Then, select the ‘Move to Project…’ option in the Actions drop-down, and choose the project you’d like the story or stories moved to:
You should see a message that the stories were moved, and there should a history entry for the move as well, both in the source and destination project. Moved stories retain comments, tasks, attachments, as well as their own history of actions.
It’s also now possible to move stories to a project via the API. Simply do a story update, with the target project’s ID in the story’s element. More on that on the API help page.
Starting Jun 30, the Twitter API will no longer allow 3rd party applications (such as Tracker) to connect using your Twitter username and password. Instead, applications will be required to use OAuth, an authentication protocol that allows users to approve a 3rd party application to act on their behalf without sharing their username/password.
Pivotal Tracker now uses OAuth for project Twitter notifications. When you enable this feature for your project (see the integrations help page for more on that), you’ll be asked to sign in to Twitter (on the Twitter site), and give the Pivotal Tracker application permission to access your Twitter account.
If you have enabled Twitter notifications for your project(s) prior to this release, the stored credentials are in the username/password format. You’ll need to remove these old credentials, by clicking the ‘Remove Twitter Credentials’ button. After you’ve done that, click the ‘Sign In With Twitter’ button to re-enable the Twitter notifications using the new, more secure OAuth way.
More information on Twitter and OAuth can be found here.
We’ll be making some DNS changes that affect Pivotal Tracker this Saturday, May 29, at 10:00am PDT. We expect a fairly short outage, but for some users, Tracker may be unavailable for up to 6 hours.
Pivotal Labs has been at the forefront of agile development since it’s early days. We’ve taken what we’ve learned by applying agile concepts on a countless number of real world projects, and honed these skills into a very effective way to build software. Along the way, we also built a great project management and collaboration tool – Pivotal Tracker.
Not only does Tracker serve as a critical component of our own development process, it’s also relied on by thousands of teams out there in the world, from open source developers, to fast growing startups, and high profile, established companies.
It’s a great app, yet we have lots of ideas for how we’d like to improve it. Want to help us? If you’re a Ruby on Rails developer, enthusiastic about agile development, and want to help us to take Tracker to the next level, read on.
If you’re interested in working with us, please send your current resume to firstname.lastname@example.org, and tell us a little about yourself. Principals only, please.
Our friends at Carbon Five have just announced Story Mapper, a release planning tool for your Pivotal Tracker projects. Story Mapper uses the Tracker API, and allows you to plan and manage your project milestones and releases at a high level. We’ve already begun to use Story Mapper on our projects at Pivotal Labs, and are excited about how well the tool complements Tracker and our planning process.
Check out Carbon Five’s blog post on Story Mapper to find out more, and to start using it today.
SnapABug, a tool that allows you to embed a screen capture help widget on your site, has taken advantage of the recently released new version of the Pivotal Tracker API (V3) to improve the integration between SnapABug and Pivotal Tracker. SnapABug can now automatically upload web page snapshots as Tracker story file attachments.
Read more about this feature and other improvements here.
We’ve added Zendesk to the list of applications that Tracker integrates with. Zendesk is a “beautifully simple”, on demand customer support help desk system. This integration allows your development team to prioritize and collaborate around Zendesk tickets as linked Tracker stories, bringing development and support closer together in your organization.
To learn how to set up Zendesk integration for your project, visit the integrations help page. Once enabled, you’ll see a new panel in your project, allowing you to see and drag/drop Zendek tickets into the backlog or icebox. Story comments and state changes will appear in the corresponding Zendesk ticket as comments.
Note: At the moment, the Pivotal Tracker target in Zendesk does not create linked stories in Tracker. We’re working with Zendesk to enable that, and make the two integrations seamless.
Pivotal Tracker will be down for an upgrade tonight, Friday (2/12/10), starting at 7pm PST. We anticipate to be back up within about an hour.
Apologies for any inconvenience.
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.
This is a new version of the API. As part of this release, the first version of the API (V1) has been removed. You can continue to use V2, but that version will deprecated at some point in the future.
Highlights of what’s new in API V3:
Tracker can now post notifications to a URL you specify as story activity happens in your project. The POST body of these requests will contain XML describing the event, as well as the affected story, in the exact same format as the API activity response.
One way to use the web hooks is for integration, to keep stories synchronized with resources in other systems. We’re hoping you’ll find other interesting ways to use them.
Activity web hooks can be enabled on your project’s Integrations page. To get there, go to your project settings, and click on the Integrations tab at the top right. More information on activity web hooks, as well as other types integration are available on the Integrations help page.
The objective of these integrations is to allow your team to prioritize, and collaborate around stories that are tied to existing tickets/issues in other systems, increasing overall visibility without having to do manual double entry. For the JIRA and Lighthouse integrations, changes to story states, and new comments will be reflected in the linked ticket/issue.
In the first release of integrations, story – ticket synchronization is 1 way only (Tracker -> JIRA/Lighthouse), but it’s possible to make that 2 way by using the Tracker API, and Lighthouse web hooks or a JIRA plugin.
See the Integrations help page for more on integrations, and how to set them up for your project.
You can now see activity from your Tracker project in your Campfire chat room.
Read more about the Campfire integration on the on the Integrations help page
As always, we welcome your feedback. If you have something that you’ve created with the API, and would like to share it with our user community, please let us know!
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:
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.