search

josephwegner / carrick-issues-tracker

Issues Tracker for Carrick Integrations
0 stars 0 forks source link

Carrick doesn't track/update transferred issues #8

Closed CLBarajas closed 4 years ago

CLBarajas commented 4 years ago

Bug description: If you transfer an issue between repositories in GitHub, Carrick fails to track it

Steps to reproduce:

  1. Link an existing GitHub issue using Carrick sidebar app in Help Scout
  2. View issue in GitHub
  3. Transfer to another repository

Expected behavior: Issue info updated in sidebar app when refreshing conversation.

Observed issue: Internal Server Error

Additional data: In my setup, both repositories' issues have allowed access to Carrick.

CLBarajas commented 4 years ago

For more context here, our team uses two separate repositories: a support repo that tracks general issues that need further verification or testing, and a main repo that does all of our development planning. When a support issue is verified to be a bug report or feature request, it gets transferred into the main repo and prioritized along with other work - and that breaks the Carrick Issues connection between GitHub and Help Scout.

josephwegner commented 4 years ago

This should be done, but waiting on #5 and multiple-linked-issues to ship first.

josephwegner commented 4 years ago

Shipped.