Discussion

Counts an anonymous vote twice after the cookie is reset — reproduced on two machines. Expected: the markdown editor keeps its state. Actual: it silently truncates long titles.

Throws a hydration mismatch in Safari — reproduced on two machines. Expected: the search keeps its state. Actual: it leaks the previous org's data into the picker.

It would pay for itself in the first month. Our support volume would drop noticeably if this shipped. It would remove the last manual step before we can automate this. What we…

The workaround breaks as soon as a second person is involved. Customers ask about this on nearly every onboarding call.

We are working around it with a spreadsheet, which is not sustainable. A rough first version would already be a big improvement.

This blocks the quarterly report we send to the exec team. It would remove the last manual step before we can automate this.

Customers ask about this on nearly every onboarding call. This has come up in three separate customer calls this month.

It would pay for itself in the first month. Not urgent, but it would save everyone about an hour a week. It was the first thing our new hires tripped over. What we would need:…

We hit this every Monday during the weekly review. It would cut a full step out of our triage loop. What we would need: Multi-language content Dark mode Custom domains

Not urgent, but it would save everyone about an hour a week. The workaround breaks as soon as a second person is involved. This is table stakes in every competing product we…

Sends two emails for a single status change — reproduced on two machines. Expected: the inbox keeps its state. Actual: it leaks the previous org's data into the picker.

It is the single biggest reason our team still keeps a second tool open. It would remove the last manual step before we can automate this. Right now this costs us roughly two…

A rough first version would already be a big improvement. We are working around it with a spreadsheet, which is not sustainable. Not urgent, but it would save everyone about an…

We have a Zapier hack doing this today and it breaks weekly. Screenshots are attached in the thread below. This blocks the quarterly report we send to the exec team.

Drops the selected filter on back-navigation — reproduced on two machines. Expected: the dashboard keeps its state. Actual: it renders the wrong timezone.

It would let us retire an internal tool nobody wants to maintain. It is the single biggest reason our team still keeps a second tool open.

It was the first thing our new hires tripped over. It would remove the last manual step before we can automate this. What we would need: An audit log Custom fields

Two people on the team have independently asked for this. We hit this every Monday during the weekly review. Our support volume would drop noticeably if this shipped.

Sends two emails for a single status change — reproduced on two machines. Expected: the roadmap keeps its state. Actual: it rejects valid email addresses containing a plus sign.

Our response times would improve without adding headcount. Our support volume would drop noticeably if this shipped. This is the difference between a nice-to-have and a daily…

It would pay for itself in the first month. Happy to test a beta build if that helps. It would let us retire an internal tool nobody wants to maintain. What we would need: A…

Breaks the layout below 380px — reproduced on two machines. Expected: the public site keeps its state. Actual: it escapes markdown twice.

Our response times would improve without adding headcount. It would let us retire an internal tool nobody wants to maintain.

Throws a hydration mismatch in Safari — reproduced on two machines. Expected: the outbound webhooks keeps its state. Actual: it returns a 500 after the first page.

It would cut a full step out of our triage loop. This has come up in three separate customer calls this month. We would move our whole team over if this landed. What we would…