Product teams often need in-product NPS and feedback — a pulse inside the app, docs, or onboarding flow — without standing up another CX stack that support and ops never open.
If your service backbone is already Jira Service Management, Myra lets you embed surveys and score widgets on external product surfaces while keeping every response native to Jira.
The product-team job
You want to know:
- Would customers recommend us? (NPS)
- Was this experience satisfactory? (CSAT)
- Was this flow hard? (CES)
…at the moment they are in the product — not weeks later in an email they ignore.
You also want one place where product, support, and leadership can act on the same scores. That place, for many Atlassian shops, is Jira.
How embeds fit Myra
Myra is built for JSM first, then extends outward:
- Configure CSAT, NPS, CES, or a custom survey in your JSM project.
- Embed the Myra widget on any product page, marketing site, docs, or status page.
- Store responses in Jira — same tenant, same operational spine as your service work.
- Optionally publish live score badges (trust signals) where prospects or users should see proof.
Project- or public-scoped surveys are what power external embeds and public score displays. Request-scoped surveys stay tied to individual tickets in the portal.
Why product teams use this instead of a generic form tool
| Need | Generic embed / form SaaS | Myra |
|---|---|---|
| In-product NPS / feedback widget | Yes | Yes |
| Data next to JSM service work | Usually a sync project | Native by design |
| Support can follow up in Jira | Manual or brittle | Same system of record |
| Trust badges from live scores | Rarely tied to JSM | Built for live score display |
| Extra vendor for feedback storage | Often yes | No — Forge / Atlassian tenant |
If product owns the widget and support owns the ticket, a split database creates two truths. Embedding into Jira keeps one.
Sensible rollout for product orgs
- Start with NPS (or CSAT) on one high-traffic surface — post-login home, checkout success, or docs “was this helpful”.
- Keep the ask short; optional comment for qualitative signal.
- Route detractors / low scores into Jira follow-up so product and support share recovery work.
- Add a live score badge only after you trust the rolling window and scope.
- Expand to more surfaces once response quality looks real.
Who this is (and isn’t) for
Good fit when product and service already meet in Atlassian — JSM is the system of record, and you want in-product feedback without a second feedback home.
Look elsewhere if you need a full product-analytics suite (session replay, feature flags, experimentation) and feedback is only a side feature. Myra is a feedback layer for JSM, not a replacement for product analytics.
Get started
Install Myra from the Atlassian Marketplace, create a project- or public-scoped NPS survey, and drop the embed on one product surface. Free to try — plans from $10 USD/month.