Developer Experience

Not urgent, but it would save everyone about an hour a week. This is the difference between a nice-to-have and a daily driver. Right now this costs us roughly two hours a week.

It would remove the last manual step before we can automate this. The workaround breaks as soon as a second person is involved. What we would need: An offline mode A Linear…

The current flow takes six clicks; it should take one. This has come up in three separate customer calls this month.

We raised this during the pilot and it is still the main gap. The workaround breaks as soon as a second person is involved. What we would need: A Linear two-way sync Saved filters

It would cut a full step out of our triage loop. Customers ask about this on nearly every onboarding call.

This blocks the quarterly report we send to the exec team. We are working around it with a spreadsheet, which is not sustainable. What we would need: An offline mode A Chrome…

Leaks the previous org's data into the picker — reproduced on two machines. Expected: the vote button keeps its state. Actual: it shows a stale vote count until a hard refresh.

Happy to test a beta build if that helps. We would stop exporting to a spreadsheet every Friday. What we would need: Role-based permissions SAML SSO Scheduled digests

It would let us retire an internal tool nobody wants to maintain. This has come up in three separate customer calls this month. Our response times would improve without adding…

Right now this costs us roughly two hours a week. This blocks the quarterly report we send to the exec team.

We raised this during the pilot and it is still the main gap. It would cut a full step out of our triage loop.

The current flow takes six clicks; it should take one. Right now this costs us roughly two hours a week. We would stop exporting to a spreadsheet every Friday.

We hit this every Monday during the weekly review. We are working around it with a spreadsheet, which is not sustainable. What we would need: Board-level moderation Keyboard…

Two people on the team have independently asked for this. We would stop exporting to a spreadsheet every Friday. Our ops team has a runbook step purely to work around it.

Even a read-only version would unblock us. Our response times would improve without adding headcount.

We are working around it with a spreadsheet, which is not sustainable. It would cut a full step out of our triage loop. Our ops team has a runbook step purely to work around it.…

Our ops team has a runbook step purely to work around it. We are working around it with a spreadsheet, which is not sustainable. This is table stakes in every competing product we…

It would cut a full step out of our triage loop. We would stop exporting to a spreadsheet every Friday. What we would need: An offline mode Webhook retries Attachment uploads A…

Our support volume would drop noticeably if this shipped. Even shipping it behind a flag would let us validate the approach. What we would need: CSV export Vote weighting Reaction…

It would let us retire an internal tool nobody wants to maintain. We would move our whole team over if this landed.

It would pay for itself in the first month. Even a read-only version would unblock us. The workaround breaks as soon as a second person is involved. What we would need: Post…

A rough first version would already be a big improvement. It would remove the last manual step before we can automate this.

We have a Zapier hack doing this today and it breaks weekly. The workaround breaks as soon as a second person is involved. What we would need: Duplicate detection Bulk actions…

It is the single biggest reason our team still keeps a second tool open. Happy to test a beta build if that helps.

Even a read-only version would unblock us. We hit this every Monday during the weekly review.