API Feedback

We are working around it with a spreadsheet, which is not sustainable. Happy to test a beta build if that helps.

Our ops team has a runbook step purely to work around it. It was the first thing our new hires tripped over. What we would need: An offline mode Custom fields A Chrome extension

It was the first thing our new hires tripped over. We would move our whole team over if this landed. We would stop exporting to a spreadsheet every Friday. What we would need:…

It would let us retire an internal tool nobody wants to maintain. The current flow takes six clicks; it should take one. What we would need: Granular email preferences Reaction…

Silently truncates long titles — reproduced on two machines. Expected: the SSO login keeps its state. Actual: it loses focus while typing.

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. Screenshots are attached in the thread below. The workaround breaks as soon as a second person is involved.

We are working around it with a spreadsheet, which is not sustainable. The workaround breaks as soon as a second person is involved.

This is table stakes in every competing product we evaluated. It was the first thing our new hires tripped over. What we would need: Post templates Internal notes A Chrome…

We hit this every Monday during the weekly review. Our support volume would drop noticeably if this shipped. 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. Not urgent, but it would save everyone about an hour a week.

This blocks the quarterly report we send to the exec team. It is the single biggest reason our team still keeps a second tool open.

Ignores the sort order on mobile — reproduced on two machines. Expected: the outbound webhooks keeps its state. Actual: it returns a 500 after the first page.

Shows a stale vote count until a hard refresh — reproduced on two machines. Expected: the mobile web app keeps its state. Actual: it silently truncates long titles.

It is the single biggest reason our team still keeps a second tool open. A rough first version would already be a big improvement. Screenshots are attached in the thread below.

We would stop exporting to a spreadsheet every Friday. It would remove the last manual step before we can automate this. What we would need: Dark mode Attachment uploads An audit…

This is the difference between a nice-to-have and a daily driver. It would cut a full step out of our triage loop. Not urgent, but it would save everyone about an hour a week.…

Even a read-only version would unblock us. This is the difference between a nice-to-have and a daily driver. What we would need: SAML SSO Granular email preferences Scheduled…

A rough first version would already be a big improvement. We would move our whole team over if this landed.

This blocks the quarterly report we send to the exec team. Two people on the team have independently asked for this. Our ops team has a runbook step purely to work around it. What…

We hit this every Monday during the weekly review. This has come up in three separate customer calls this month.

Our support volume would drop noticeably if this shipped. It is the single biggest reason our team still keeps a second tool open. We would stop exporting to a spreadsheet every…

This blocks the quarterly report we send to the exec team. It would cut a full step out of our triage loop. It was the first thing our new hires tripped over. What we would need:…

Our ops team has a runbook step purely to work around it. A rough first version would already be a big improvement.

It would remove the last manual step before we can automate this. This is table stakes in every competing product we evaluated.