Weekly Patch - April 12, 2026
Show Jira ID to Testers!
What we added: Testers had no way to see the Jira Issue ID associated with their feedback, which made it tough to communicate about unresolved bugs using a shared reference point. Now there's a toggle for that! **See it in action:
1. Go to Feedback properties of any feedback type
2. Enable the new "Show Jira ID to testers" toggle (it's off by default)
3. Testers will now see the Jira ID as plain text in the right-hand menu of the feedback view page **Good to know: The ID is shown as text only (not a clickable link). PMs and Support users (with the Manage feedback and replies role) continue to see the existing Jira link in the title area regardless of this setting. **Good to know: The ID is shown as text only (not a clickable link). PMs and Support users (with the Manage feedback and replies role) continue to see the existing Jira link in the title area regardless of this setting.
Community and Project Homes
"Restore Content" Button Now Persists After Page Refresh**What we fixed: When testers dismissed content on a project or community homepage and then refreshed the page, the "Restore content" button would disappear. The only way to get content back was to ask an admin to create new content — not ideal! The restore button now sticks around as long as there's dismissed content to bring back. **See it in action:
1. As a tester, visit a project or community homepage that has dismissible content
2. Click the X to dismiss a content block
3. Confirm the "Restore content" button appears
4. Refresh the page — the button should still be there, ready to bring your content back
Feedback Management
Jira Ticket IDs No Longer Visible to Participants**What we fixed: Participants were seeing Jira ticket IDs and links when viewing feedback — that's info meant for team members only! This snuck in with a recent UI update. Those Jira references are now hidden from participants again, just like they should be. **See it in action:
1. Navigate to a feedback type that has a Jira integration configured
2. Assume a participant who has submitted feedback that was sent to Jira
3. Open the feedback item — you should see no Jira ID or links anywhere in the ticket view (unless the new setting above is enabled for that project)
Integrations
Jira Integration Now Supports Separate Public Domains**What we fixed: Some customers use a different public-facing Jira URL than their API domain (e.g., their team browses Jira at one address, but the API lives at another). Our integration previously assumed these were the same. We've added support for configuring a separate public domain so Jira links generated by the platform point to the right place. **See it in action:
1. Navigate to a Jira external destination configuration
2. Look for the new public domain field
3. If the customer's public Jira URL differs from their API URL, enter it here — links in the platform will now use this domain