2-way sync with Pivotal Tracker

[brentonw]

Problem Statement

With today's Pivotal Tracker integration, data is no longer synced between Pivotal Tracker and Sentry after creating a Pivotal Tracker bug from a Sentry Issue.

For example:

• resolving a bug in Pivotal Tracker, doesn't mark the issue as resolved in Sentry
• assigning a person in Pivotal Tracker doesn't assign a person in Sentry

This means issues need to be managed from 2 locations, not just 1.

Solution Brainstorm

Our desired workflow is to use Sentry for issue report collection and triage. Once it's determined to be a bug we'll fix, our workflow moves to Pivotal Tracker.

It would be great if changes we make in Pivotal Tracker could be reflected in Sentry to avoid having to mark issues as resolved twice, ie once in Pivotal Tracker and once in Sentry.

Likewise, if we were to make changes in Sentry, such as marking an issue resolved or assigning it to someone, those changes should also be able to propagate to a linked work item in Pivotal Tracker.

[getsantry[bot]]

Assigning to @getsentry/support for routing, due by Friday, February 10th at 17:00 (yyz). ⏲️

[getsantry[bot]]

Routing to @getsentry/ecosystem for triage, due by Monday, February 13th at 5:00 pm (sfo). ⏲️

[therealarkin]

Thanks, @brentonw! TBH, our most popular integrations in the space are Jira, Trello, Asana, and Pivotal comes at a distance 4th [internal link for future reference]; so it's not something we going to prioritize soon. However, since it's open source you can certainly ask Pivotal to improve that integration. I know it's not a super satisfying answer, but we need to prioritize internally improvement in the popular integrations vs the one that are used less.

[therealarkin]

I'll leave this open to get feedback from other members of the community and/or Pivotal