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

It is the single biggest reason our team still keeps a second tool open. It would pay for itself in the first month. We hit this every Monday during the weekly review.

The current flow takes six clicks; it should take one. It is the single biggest reason our team still keeps a second tool open. Not urgent, but it would save everyone about an…

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.

Right now this costs us roughly two hours a week. Even shipping it behind a flag would let us validate the approach. It would cut a full step out of our triage loop.

This blocks the quarterly report we send to the exec team. Right now this costs us roughly two hours a week. It would cut a full step out of our triage loop.

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.

Our ops team has a runbook step purely to work around it. Our support volume would drop noticeably if this shipped. Two people on the team have independently asked for this.

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…

A rough first version would already be a big improvement. Happy to test a beta build if that helps. Two people on the team have independently asked for this.

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.

Screenshots are attached in the thread below. A rough first version would already be a big improvement. What we would need: A public API rate-limit dashboard Board-level…

Screenshots are attached in the thread below. Right now this costs us roughly two hours a week. It would cut a full step out of our triage loop.

It would let us retire an internal tool nobody wants to maintain. It would remove the last manual step before we can automate this.

We would stop exporting to a spreadsheet every Friday. We are working around it with a spreadsheet, which is not sustainable. What we would need: Internal notes Board-level…

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 have a Zapier hack doing this today and it breaks weekly. Right now this costs us roughly two hours a week. Even shipping it behind a flag would let us validate the approach.…

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.

This blocks the quarterly report we send to the exec team. Happy to test a beta build if that helps. What we would need: Reaction emoji Multi-language content Slack notifications

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…

The workaround breaks as soon as a second person is involved. It would cut a full step out of our triage loop. This has come up in three separate customer calls this month. What…

It was the first thing our new hires tripped over. It would pay for itself in the first month. It would let us retire an internal tool nobody wants to maintain.