Productlane is the first platform that combines a feedback hub with customer support and integrates all that tightly into Linear. The core concept is that everything in Productlane is about your customers and their feedback, and every feature idea should live in Linear.
Threads are emails, Slack messages, survey results and all your other feedback. Depending on the thread source, they consist of an editable notes field at the top and a thread below, where you can comment or answer via email or slack, if you connected it. The main action you will to on threads is to reply and link them to Linear issues or projects.
We believe, your issue tracker is the best place to centralize all your ideas. From the beginning, when they are still observations, until the very end, when they are fully fledged out projects with milestones and todos, ready to be built and bring value to the world.Priorities are constantly shifting. That’s why, if you keep an opportunity backlog separate from Linear, you will have a lot of duplicate work over time.
Some ideas should be built right away as they are easy to do, some fully planned out projects on your roadmap turn out too ambitioned and should be put back into an idea state, as the solution to the problem turns out wrong, or the problem turns out not being important enough.
If everything is in Linear, it’s very easy to shift things around, and you will keep the full overview all the time.
Another core concept of Productlane is helping you close the loop. That way you can make sure that you really implemented it and the customers know that their feedback mattered. If you connect a thread to Linear and mark it as done, the thread will move back to your inbox as soon as the linked issues or project is completed in Linear.
Create a Linear 'Feature requests' team
So, yes, we recommend to keep every idea in Linear. We recommend creating a separate “Feature requests” team in Linear to avoid cluttering your backlog and not confuse engineers about what should be built and what not.
When to use tags
We suggest to use tags for everything that’s not actionable. If you’re a user researcher or you’re doing a lot of interviews, we also suggest using tags for your observations. You can turn them later into Linear issues or projects when they are ready. At Productlane, we use tags for example to track signup, upgrade and churn reasons and competitor mentions on a continuous basis.
How to display feedback directly in Linear
You can even directly display the feedback count from Productlane in Linear, by activating the “Links” property in the Linear display settings: