[evaneykelen]

I’m working on TaskSift which, although it’s not a pure issue tracker, does use a mix of sources like email, github, etc as its source of truth when it comes to issue status.

We struggled quite a bit with getting this status thing right, finally settling for model where user stories inside TaskSift are based on multiple inbound tickets (each with a different status), and where each story can be published eg to GitHub, QA queue, an l10n tool, etc again each with its own status and completion time.

Once all published tasks are finished the folks who contributed to the inbound tickets can all be notified, and the tickets can be closed, either from within TS or using the tool in which the ticket was created originally (Zendesk etc).