Once a discovery is ready to build, the work moves to your engineering tool. Linking the issues back to the discovery keeps both sides connected: engineers see the customer feedback behind what they build, and product sees how far the work has gone without leaving Harvestr.
How it works
With any of the integrations below, a discovery gets a section for the tool. From there you can:
create a new issue or card, pre-filled with the discovery's title and description if you want, and a link back to Harvestr
link issues that already exist
follow their status from the discovery, and from your discovery views
You can link as many issues as you need to one discovery, and even mix tools.
Which tool does what
Tool | Create and link issues | Update the discovery's state automatically |
Yes | Yes | |
Yes | Yes | |
Yes | Yes, from a GitHub Projects board | |
Yes | No | |
Yes | No |
All five are available on every paid plan. Jira Server and Data Center need the Elite plan.
Keep discovery states in sync
With Jira, Linear and GitHub, you can stop updating states by hand. On each integration's settings page, the Discovery automations card lets you create rules such as: when all linked issues are Done, set the discovery to Shipped.
It pays off twice: your roadmap stays current, and the teammates who submitted the feedback hear about it, since a state change can trigger feedback loop notifications.
Track the work from your views
Add the issues field of your tool to a discovery view to see, at a glance, which discoveries are in development and where their issues stand. Two views worth saving:
In development: discoveries with at least one linked issue
Shipped in the tool, not in Harvestr: discoveries whose issues are done but whose state hasn't moved, if you don't use automations
A good habit
Create the issue from the discovery rather than in your engineering tool. It takes the same time, and the issue carries a link back to the customer feedback, so engineers can read what customers actually said before they build.