JSM's native Surveys feature: when it's enough, and when you need a Forge app

[#1]

Jira Service Management shipped a native Surveys feature in March 2026 (announcement, docs), and it's a real upgrade over the old CSAT-only setup: flexible question types, privacy controls, feedback across services and lifecycle moments (not just "how was your ticket"), all without leaving Jira. If you've been eyeing a third-party survey app purely to get past basic CSAT, it's worth checking whether native Surveys already covers you before you buy anything.

It doesn't cover everything, though, and the gap is specific enough to be worth naming rather than hand-waving. A few weeks after launch, a service team asked Atlassian directly whether Surveys had a submission trigger for Automation, or survey-specific smart values, so a bad response could kick off a follow-up ticket automatically. Atlassian's own team confirmed: not yet.

Today, survey responses live in the Surveys UI (or a CSV export) and nowhere else - no automation trigger, no smart values to reference in a rule. You can collect broader feedback natively now. You can't yet act on it natively.

That gap is really the whole decision, so here's the three-way framework I use when someone asks which way to go:

Stay native if: you need CSAT (or the new broader Surveys use cases - onboarding check-ins, employee pulse surveys, service quality) and you're fine reviewing responses manually or exporting to CSV for reporting. No NPS/CES out of the box, no branching logic beyond what Forms supports, no way to trigger a Jira action off a bad score yet. For a lot of teams, especially ones just starting to measure satisfaction at all, that's genuinely enough - don't add a tool you don't need.

Add a Forge app if: you need any of - NPS or CES alongside CSAT, conditional/branching survey logic, an embeddable live score badge outside Jira, or (the big one) a bad response automatically creating or linking a Jira issue for follow-up. Forge apps run inside your Atlassian tenant, so this doesn't mean giving up the "data stays in Jira" property that made native Surveys appealing in the first place - it means adding the operational layer native Surveys doesn't have yet.

Go external (Typeform, SurveyMonkey, etc.) if: your team already lives there for other reasons, or you need things like panel research or feedback orchestration across non-Atlassian products. The tradeoff is data sprawl - responses live outside Jira, and you're back to the "switching between tools" problem native Surveys was built to solve.

If you land in the middle bucket, a few things are worth checking before picking anything: does it actually trigger a Jira issue on a low score, or just log the score somewhere for you to review later? Does it support NPS/CES if you need them, not just CSAT? Is it Forge-native (data stays in your tenant) or does it phone home to an external service? A couple of these differ meaningfully between apps in this category, so it's worth trying more than one in a sandbox rather than picking off the Marketplace listing alone.

Full disclosure: I work on Myra, a Forge app in this space - CSAT/NPS/CES surveys, low scores auto-linking to a Jira issue, and embeddable score badges. Mentioning it here because it's a direct example of the "add a Forge app" branch above, not because it's the only option - there are others, and the right pick depends on which of the gaps above actually matter to your team.

Curious whether anyone's found a way to wire native Surveys into Automation despite the current limits - if Atlassian's shipped something on this since March, I'd genuinely like to know.

[Attila Bódis]

nice :)