Integrations

Bug & feature pipeline

Problems and requests raised inside OppFlow become tracked items in engineering's own system, rather than an email someone has to remember.

Two routes in, and they are not the same

This distinction is worth knowing, because the two behave differently:

The Support form

Question, bug or feature request, typed by you on the Support page. It opens a support ticket — a conversation with the OppFlow team, which you can follow and reply to.

Detected issues

The badge in the command bar. The app notices its own failures — a failed API call, a render error — and queues them with the error and the route already attached. This is the queue that feeds the automated pipeline.

A bug filed through the Support form points you at the detected-issues panel as a next step, because an issue captured with its own error text is far more actionable than a description of it.

What happens to a detected issue

It is de-duplicated against what has already been reported, then opened as an issue in the engineering repository. The issue's identity is stored back on the report, so status follows the real work rather than being retyped.

Feature requests carry votes

Requests become discussion threads, and they can be voted on: the same request from several workspaces is one thread with a count, not five duplicates.

It runs in both directions

The knowledge-base articles the Support page serves are authored as wiki pages and discussions in that same repository and synced in by webhook. That is why a help article can be corrected without shipping a release, and why you will never find one as a file in the product.

Why this is listed as partial

The automated half degrades to a no-op when the engineering-side credentials are not configured on a deployment. Your report is still recorded and still reaches support; it simply does not open an issue by itself. Nothing is lost, but the round trip is manual.

What a report carries

The page you were on and recent console output are attached, so the first question back is not “what were you doing?”. Read the form before you send if that matters to you.

OppFlow.ai docs · by Traversal · v0.1.32