Feedback

Mobile Feedback

Mobile Feedback for Mobile Apps.

It was the first thing our new hires tripped over. Even shipping it behind a flag would let us validate the approach.

Feature8

Leaks the previous org's data into the picker — reproduced on two machines. Expected: the public site keeps its state. Actual: it silently truncates long titles.

BugMobile4

This is the difference between a nice-to-have and a daily driver. This is table stakes in every competing product we evaluated. We raised this during the pilot and it is still the…

Feature2

The workaround breaks as soon as a second person is involved. This blocks the quarterly report we send to the exec team. Happy to test a beta build if that helps. What we would…

FeatureMobile2

We are working around it with a spreadsheet, which is not sustainable. This is the difference between a nice-to-have and a daily driver. Our ops team has a runbook step purely to…

Feature9

Our response times would improve without adding headcount. We hit this every Monday during the weekly review. It would pay for itself in the first month. What we would need:…

FeatureIntegrations8

Our ops team has a runbook step purely to work around it. Two people on the team have independently asked for this.

FeatureUI & Design0

We raised this during the pilot and it is still the main gap. This is the difference between a nice-to-have and a daily driver. Even a read-only version would unblock us. What we…

FeaturePerformance1

Add SAML SSO

Resolved

We would stop exporting to a spreadsheet every Friday. A rough first version would already be a big improvement. What we would need: Custom domains MRR-weighted prioritisation An…

Feature10

Even a read-only version would unblock us. We would stop exporting to a spreadsheet every Friday. The workaround breaks as soon as a second person is involved. What we would need:…

Feature6

It would let us retire an internal tool nobody wants to maintain. Not urgent, but it would save everyone about an hour a week. Our support volume would drop noticeably if this…

FeatureIntegrations15

This is table stakes in every competing product we evaluated. We would stop exporting to a spreadsheet every Friday. We have a Zapier hack doing this today and it breaks weekly.…

Feature0

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

Feature3

Right now this costs us roughly two hours a week. We are working around it with a spreadsheet, which is not sustainable. What we would need: Post templates Bulk actions A public…

Feature7

We are working around it with a spreadsheet, which is not sustainable. This is the difference between a nice-to-have and a daily driver. Even a read-only version would unblock us.…

Feature1

This blocks the quarterly report we send to the exec team. This has come up in three separate customer calls this month.

FeatureIntegrations2

We would move our whole team over if this landed. It would let us retire an internal tool nobody wants to maintain. We raised this during the pilot and it is still the main gap.

FeatureUI & Design0

Even shipping it behind a flag would let us validate the approach. Our ops team has a runbook step purely to work around it. Screenshots are attached in the thread below. What we…

FeaturePerformance1

This is the difference between a nice-to-have and a daily driver. This is table stakes in every competing product we evaluated. Our response times would improve without adding…

FeatureMobile9

We would move our whole team over if this landed. Our response times would improve without adding headcount.

FeatureMobile0

This has come up in three separate customer calls this month. Our ops team has a runbook step purely to work around it. What we would need: An audit log SAML SSO A Linear two-way…

FeatureMobile2