Pivotal Tracker + Runway

Tickets in Pivotal Tracker are only half of the picture

It’s release time – do you know where your code is? 🚨 The state of tickets in Pivotal Tracker tell some of the story, but how do you know if corresponding code has been merged, or whether a given build contains the work? Without a single source of truth, teams fall back on taxing back-and-forths over Slack and bouncing between browser tabs. Runway brings everything into one place: at a glance, alongside your Pivotal Tracker work, see commits and PRs, builds, stability info, and more.

Abstract Runway UI showing lots of assorted and important info about a release

Runway’s automatic ticket labeling lets you trust Pivotal

Your entire team is wasting time making sure tickets in Pivotal Tracker have the appropriate label for each release – and, inevitably, some tickets are missed, leading to an incomplete and untrustworthy picture of work. Runway helps you rebuild that trust, by automatically applying the expected labels to any tickets that are missing them, for each and every release.

A clear view of how your release stands, no digging required

Your entire team shouldn’t need to constantly filter through labels in Pivotal to understand what’s happening at a glance on a release level. Runway intelligently shows you exactly what you need to see, with granular filtering and sorting that allows your team to further customize the view as needed.

With Runway, showstoppers are actually showstoppers

Ambiguity around critical fixes leads to more bugs and lower quality overall. With Runway, when you create a bug ticket in Pivotal Tracker and mark it P0 for a given release, it’s clearly highlighted as pending work and will block that release cycle until it’s addressed. The whole team will see live progress as code is written against the bug, as builds containing the fix are created, and as the fix is validated by QA.