Feature Requests

We hit this every Monday during the weekly review. It would pay for itself in the first month. Right now this costs us roughly two hours a week.

We would move our whole team over if this landed. Screenshots are attached in the thread below. What we would need: Zapier triggers A Linear two-way sync Webhook retries

Not urgent, but it would save everyone about an hour a week. Right now this costs us roughly two hours a week. Our ops team has a runbook step purely to work around it.

Never clears the loading spinner — reproduced on two machines. Expected: the inbox keeps its state. Actual: it shows a stale vote count until a hard refresh.

We would move our whole team over if this landed. Even shipping it behind a flag would let us validate the approach. It would let us retire an internal tool nobody wants to…

Right now this costs us roughly two hours a week. This blocks the quarterly report we send to the exec team. This is the difference between a nice-to-have and a daily driver.

Even a read-only version would unblock us. Our support volume would drop noticeably if this shipped. What we would need: Granular email preferences An audit log

This is the difference between a nice-to-have and a daily driver. It would cut a full step out of our triage loop. What we would need: Post templates Zapier triggers Dark mode

We raised this during the pilot and it is still the main gap. It would let us retire an internal tool nobody wants to maintain. Customers ask about this on nearly every onboarding…

Screenshots are attached in the thread below. We would stop exporting to a spreadsheet every Friday. Happy to test a beta build if that helps.

Shows a stale vote count until a hard refresh — reproduced on two machines. Expected: the settings page keeps its state. Actual: it counts an anonymous vote twice after the cookie…

It would cut a full step out of our triage loop. It is the single biggest reason our team still keeps a second tool open. What we would need: An RSS feed Custom fields A Linear…

A rough first version would already be a big improvement. Our ops team has a runbook step purely to work around it. We have a Zapier hack doing this today and it breaks weekly.

Happy to test a beta build if that helps. We raised this during the pilot and it is still the main gap. What we would need: An offline mode Keyboard shortcuts

Two people on the team have independently asked for this. Our response times would improve without adding headcount. This has come up in three separate customer calls this month.

Counts an anonymous vote twice after the cookie is reset — reproduced on two machines. Expected: the keyboard shortcuts keeps its state. Actual: it sends two emails for a single…

This is the difference between a nice-to-have and a daily driver. Our ops team has a runbook step purely to work around it. Even a read-only version would unblock us.

Two people on the team have independently asked for this. Even a read-only version would unblock us. This is table stakes in every competing product we evaluated. What we would…

Screenshots are attached in the thread below. The workaround breaks as soon as a second person is involved.

Our response times would improve without adding headcount. We are working around it with a spreadsheet, which is not sustainable. This is table stakes in every competing product…

This blocks the quarterly report we send to the exec team. We would stop exporting to a spreadsheet every Friday.

Our support volume would drop noticeably if this shipped. Customers ask about this on nearly every onboarding call.