Tags
Cluster your support volume with tags, grouped into sets.
How it works
We recommend using tags for everything that’s not immediately actionable. There are usually more observations in user interviews or feedback that you want to keep track of. Tag groups give you a way to cluster these. You could use these tag groups:
Bug, feedback or question
Competitor mentions
Signup reasons (We send all automated survey results to Productlane)
Upgrade reasons
Churn reasons
Turn tags into Linear issues or projects quickly
If anything actionable found it’s way into the tags, you can convert it anytime to a Linear project or issue. If you open a tag, you can turn it into a Linear issue or project really quickly and keep all the connected thread links.
Was this helpful?