🐞  Bug Fixes 🐞 

Data Engine & Custom Reports

Report Creation From Feedback Management Page Now Works Properly

What we fixed: When clicking "Create a report" directly from the Feedback management page, the second series and filter dropdowns weren't populating correctly.

See it in action:

1. Navigate to the Feedback management page

2. Mouse over a feedback type and click "Create a report"

3. The second series and filter dropdowns now populate correctly

New CDE Columns: Phase Started and Phase Ended

What we fixed: The CDE Feature Engagement section was missing phase start and end date columns, so there was no way to see when a phase began or ended in data exports. Two new columns, "Phase started" and "Phase ended", are now available.

See it in action:

1. Navigate to a data export that includes CDE Feature Engagement data

2. Look for the new "Phase started" and "Phase ended" columns

3. All features within the same phase will show the same dates — features with no phase association will show blank values

Integrations

File Duplication Fixed for API-Uploaded Feedback Attachments

What we fixed: If a feedback ticket was created via an external source with multiple files uploaded through the API, those files could appear duplicated whenever the ticket's status was changed by an external listener macro. Even worse, the duplication compounded with each subsequent status change, so files could multiply quickly.

See it in action:

1. Create a feedback ticket via an external source (e.g., Jira sync)

2. Upload multiple files to the ticket through the API

3. Trigger a status change via an external listener macro

4. Files now display correctly without any duplication, no matter how many status changes happen 🎉

Onboarding/Recruiting

Recruiting Landing Page No Longer Creates Broken Invite Types

What we fixed: Editing the "Invited manually via teams" invite type to add a landing page was creating a recruitment in a weird, half-broken state. The recruitment would show only the landing page, and any invites added to it would become invisible (though they were still technically functional and eating up invite URLs behind the scenes).

See it in action:

1. Invite a user to a project via teams

2. Can no longer Click Edit on the "Invited manually via teams" invite type!

Test Planning

Unpublished Engagement Phases No Longer Show "In Test"

What we fixed: Creating an engagement phase for the current date and unpublishing it was causing the project to show up as "In test" on the community home page. This could confuse testers since there was no active phase to participate in.

See it in action:

1. Create an engagement phase dated for today but leave it unpublished

2. Navigate to the community home page

3. The project no longer incorrectly displays as "In test"

Good to know: This also applies to Onboarding and Closure phase messaging on the community homepage.

Miscellaneous

WYSIWYG "Code" Style Formatting Now Matches Preview

What we fixed: The "Code" style in the WYSIWYG editor was looking great while you were editing, but then rendered completely differently once published. Multi-line code blocks were especially affected.

See it in action:

1. Open any WYSIWYG editor field

2. Type some multi-line text and apply the "Code" style

3. Save and view the published result, it now matches what you saw in the editor

Content View Counters Now Track Homepage Views

What we fixed: Content items set to "Show on Home Page" were rendering just fine on the Project Home Page, but their view counters stubbornly stayed at zero. Views were only being counted when someone clicked through to the individual content page. Now, views are tracked for content displayed in both the main content list and the "What's New" section on the homepage.

See it in action:

1. Set a content item to "Show on Home Page"

2. Visit the Project Home Page as a tester (the content renders inline)

3. Check the view count — it now increments! Refreshing the page within the same session won't double-count.

Good to know: A view is a view regardless of where it was seen. If someone views content on the homepage and then clicks into the full page, it only counts once per session.

We've been hard at work on a major overhaul of AI-powered feedback tools, and this month they're officially out of GoEarly and into production for everyone. And there's already something new blooming in the GoEarly pipeline: AI Feedback Submission is heading into early access, giving community members a whole new way to share what they're thinking. Want in early? Get signed up now!

 new features

✨ New Features ✨

Reimagined Feedback View

The feedback list has a new look, and it's more than cosmetic. We've overhauled the Feedback View to make navigating and acting on feedback faster, with a cleaner layout and a more consistent experience across the board. Whether you're triaging a full queue or digging into a single ticket, you'll find the controls where you expect them and the information you need front and center.

AI Feedback Summary and AI Discussion Summary

Ted now reads your tickets so you don't have to start from scratch. Two new AI Summary fields are available in Feedback: one that condenses the full ticket into a quick overview, and one that summarizes the entire comment thread separately. Walk into any piece of feedback already up to speed, even if the discussion has been running for weeks.

Both summaries live right on the feedback card and are accessible from two places: expand any card in the feedback list and click the Toggle AI summary button to see them side by side, or open an individual ticket and expand the card just below the header. The Discussion Summary is context-aware, too. It takes the Feedback Summary as input, so it's grounded in the original submission rather than treating the replies in isolation. And when a new reply comes in, the Discussion Summary regenerates automatically.

Admins can enable AI Feedback Summaries per feedback type under Management > Project Configuration > Feedback Types > Modify > Feedback Properties, with the option to add custom instructions per type. For example, you might direct the AI to focus on reproduction steps for issues or emphasize sentiment for ideas. Both summary fields are also available as view and filter columns, with full support in reports, exports, integrations, and email templates as dynamic tags. Check out the AI Feedback Summaries Overview for full setup details.

AI Reply Generator

Responding to feedback just got a lot faster. When you change the status on a feedback ticket, the AI Reply Generator automatically drafts a comment for you based on the ticket content and the status you selected. A status change to Need More Info produces a different reply than one to Fixed; the tone and content are tailored to the intent of the update.

The draft appears right in the reply field on the feedback card, accessible from both the feedback list and the individual ticket view. Review it, edit it however you like, and click Update status to post the reply and status change together. You can also clear the field entirely and submit the status update without a reply. Nothing goes out until you say so.

AI Smart Reply Drafts are enabled per feedback type under Management > Project Configuration > Feedback Types > Modify > Feedback Collection and Collaboration. Admins can also configure per-type prompt enhancements to tune the tone of generated replies, whether that's more formal for enterprise programs or more conversational for consumer ones. For full setup details, see the AI Smart Reply Drafts Overview.

Redesigned Community AI Settings

The Community AI settings page has been rebuilt from the ground up. The new design is cleaner and easier to navigate, and it comes with brand-new licensing controls that give admins more direct control over how AI features roll out across their community. If you've been wanting a clearer picture of your AI configuration, this is the page you'll want to revisit.

💡 GoEarly Features 💡

AI Feedback Submission and AI Element Enhancement

We've got two big ones headed into GoEarly this month, and both are aimed at making feedback better before it even lands in your queue.

AI Feedback Submission gives community members a new way to share what they're experiencing: they describe it in plain language using the AI Submit button in the project navbar, and AI organizes that input into one or more structured submissions automatically. Members review everything on a provisional screen before anything is finalized, with five minutes to edit, reassign, or discard. There's also a built-in duplicate check that surfaces similar existing feedback so members can vote instead of filing a new entry. On the admin side, a Show original option lets you pull up the member's unedited input alongside the structured result.

AI Element Enhancement works at the form level. Admins can mark any feedback form field as AI-generated, so after a member submits, AI automatically populates it based on the rest of the submission. A vague title becomes a clean one. A summary field fills itself in. Admins write the prompt and choose which fields feed into it; members just fill out the same form they always have.

Want early access to both? Get signed up for GoEarly now!

fixes  

🐞  Bug Fixes 🐞 

Data Engine & Custom Reports

File Exports No Longer Tripped Up by Certain File Names

What we fixed: Exporting files from a feedback type could silently produce an incomplete zip if any uploaded files had certain reserved names (like `com1.png` or `aux.txt`). The export would show the right file count in the preview, but the zip would come up short. Those files are now handled properly during export.

See it in action:

1. Go to a feedback type that has file attachments

2. Run an export that includes files

3. Check your zip, all files should be present and accounted for, regardless of their names

Onboarding/Recruiting

API Import Invitations Now Accept Custom Messages As Intended

What we fixed: When setting up an API import invitation and trying to add a custom message, the form would incorrectly throw a "Write a custom message" validation error, even though you just did! Custom messages now save as expected.

See it in action:

1. Navigate to a project's Recruiting section

2. Create or edit an API import invitation type

3. Enter a custom message and submit, it'll work without a fuss!

User Interface & Experience

Copy Tester-Facing Links from Content and Releases

What we fixed: Well, this one's brand new! Admins can now copy a tester-facing link directly from Content and Releases admin list views — no more manually editing URLs to share with testers.

See it in action:

1. Navigate to a Content or Releases admin list view

2. Click the clipboard icon on any row

3. You'll see a "Link copied!" toast — paste it wherever you need to share it with testers

Good to know: If the short link can't be created for any reason, the full tester-facing URL is copied instead, so you're always covered.

🐞  Bug Fixes 🐞 

Data Engine & Custom Reports

Rating Scale Labels Now Stick on Column Reports

What we fixed: When creating a column-style report with rating scale elements, turning on "Show labels" at the report level wasn't actually carrying through to the individual elements. So your charts would show "1, 2, 3" instead of "Poor, Fair, Good, Excellent." Now the setting propagates correctly.

See it in action:

1. Create a new report that includes a rating scale element

2. Choose the "Columns" style and enable "Show labels" under "Customize your results"

3. Save the report and your rating scale text labels should appear on the charts right away

Feedback Management

Ownership Dropdowns No Longer Default to First Person Alphabetically

What we fixed: When assigning ownership of a feedback item, the dropdown used to default to whoever came first alphabetically which meant it was easy to accidentally assign something to the wrong person without realizing it. Now it defaults to a blank placeholder, so you have to make a deliberate choice.

See it in action:

1. Open a feedback item and go to assign an owner

2. Notice the dropdown starts with a "select" item instead of a team member's name

3. Pick the person you actually want, so no more surprise assignments!

This applies to the "Assign To Member" dropdown, the Workflow "New Owner" dropdown, and the Status dropdown in view mode.

Integrations

New Dynamic Tags: Submitter and Owner User ID

What we fixed: You can now include submitter and owner user IDs in your external destination payloads. This makes it a lot easier to build integrations that link users across systems.

See it in action:

1. Go to an external destination template in the Feedback area

2. Open the dynamic tag picker and you'll see new "Submitter User ID" and "Owner User ID" tags

3. Add them to your template and fire a test, the tags resolve to each user's platform identifier

Good to know: If a feedback item doesn't have an owner assigned, the tag will just resolve to an empty value.

Miscellaneous

Duplicate Releases with Notice Setting Fixed

What we fixed: If you had a release with the "Require users to view" Notice setting turned on, it could sometimes show up twice in your project menu. Even weirder, users could get stuck bouncing between the two copies when trying to continue past the announcement. That's all cleaned up now!

See it in action:

1. Go to any project and create or edit a release

2. Enable the Notice setting with "Require users to view"

3. Check the project menu and you'll see just the one release, as expected

Fixed a Crash When Date Format Setting Was Empty

What we fixed: In some cases, if a community's date format setting wasn't configured, users could hit an error when loading their preferences. We've added a safety net so it gracefully falls back to the default format instead of crashing.

See it in action:

1. This one's behind the scenes so there is no action needed on your end

2. If you were seeing unexpected errors when navigating certain communities, those should be resolved now

🐞  Bug Fixes 🐞 

Data Engine & Custom Reporting

Age Restriction Settings Fix

What we fixed: Enabling age restriction on User Account Settings was throwing an error and not saving properly. A related filter issue with Team Type custom filters was also resolved — those should load correctly now too.

See it in action:

1. Go to your project's User Account Settings

2. Enable the age restriction option

3. Save — no more error, smooth sailing!

If you're using custom filters on Team Type views, those will also behave as expected again.

Miscellaneous

PDF Export Fix for Large Reports

What we fixed: PDF exports were timing out for larger or slower-loading reports, resulting in a 404 page instead of the actual PDF. The system now gives reports the full configured timeout to finish rendering.

See it in action:

1. Navigate to a report (especially a larger one with lots of data)

2. Export it as a PDF

3. Sit back and let it do its thing, even big reports will complete successfully now!

Avatar Cropping Fix

What we fixed: Certain images weren't playing nicely with the avatar cropping tool — if the image dimensions exceeded the container size, the crop UI wouldn't work correctly.

See it in action:

1. Go to your profile or any place you can set an avatar

2. Upload an image (even a really large one!)

3. The cropping tool will now handle it properly, no matter the dimensions

🐞  Bug Fixes 🐞 

Integrations

API Key Page Loading Error Fixed

What we fixed: Some accounts were hitting a bomb error when navigating to the API Key Management page — the page just wouldn't load at all. We tracked it down and patched the underlying cause so the page opens cleanly again.

See it in action:

1. Navigate to your account's API Key Management page.

2. Confirm the page loads without any errors.

3. Create, view, or revoke keys as normal — all good! 🎉

Form Engine & Custom Surveys

Unpublished Surveys No Longer Time Out for Large Programs

What we fixed: If you had an unpublished survey that a large number of testers had access to, loading the form view could get really slow — or even bomb out entirely. We optimized the query behind the scenes so it's no longer doing unnecessary work for surveys that haven't been published yet.

See it in action:

1. Open an unpublished survey in a program with a large tester group.

2. Navigate to the form view.

3. Confirm the page loads quickly without any timeout or bomb errors.

 Miscellaneous

Address Region Now Saves Correctly for UK (and Similar Countries)

What we fixed: When manually entering an address for countries that use sub-regions (like the UK), selecting a region and saving wasn't sticking. Even worse, the saved data was sometimes showing a completely wrong region in reporting. We've fixed both the save behavior and cleaned up any bad data left behind.

See it in action:

1. Go to a user profile and open the address fields.

2. Enter a UK address and select **England** (or any sub-region) from the Region dropdown.

3. Save the profile, then reopen it — the region should now show exactly what you selected.

4. Check reporting to confirm the region is displaying correctly there too.

💡 Centercode GoEarly Features 💡

Evolve How You Collect, View, and Triage Feedback 

This is a big one for our GoEarly participants! We've been hard at work overhauling the AI experience across Centercode, and this release is packing in three major, fully-featured additions. 

• First, we're rolling out an updated Feedback View alongside a simplified feedback list experience that makes navigating and acting on feedback faster and more consistent.
• Second, we have added new AI Summary fields in Feedback, giving you a quick run-down of the entire ticket and, separately, the feedback's ongoing discussion meaning you get an instant summary of the entire comment thread, too. 
• Third, we've provided a valuable shortcut for feedback triage! Our new AI Reply Generator creates a comment based on ticket details and selected status, enabling you to approve or edit before posting.

Of course, data captured through AI Feedback Summary and AI Discussion Summary are available as view and filter columns, with full support in reports and exports as data items, and integrations and email templates as dynamic tags. Aaaaand finally, the Community AI settings page has been completely redesigned with a fresh visual experience and brand-new licensing controls, giving admins more power over how AI features are rolled out across their community. 

Head over to GoEarly to sign up and get your hands on it early!

🐞  Bug Fixes 🐞 

Integrations

External Destinations Now Trigger Correctly for Tickets with Long Filenames

What we fixed: If a feedback ticket had a .mov file attached with a very long filename, any external destinations set up on that ticket (like Jira) would silently fail to fire — no error message, no log entry, just... nothing. Sneaky! Now EDs fire correctly regardless of how long the attachment filename is.

See it in action:

1. Attach a .mov file with a lengthy filename to a feedback item.

2. Trigger a status change that's configured to send that feedback to an external destination.

3. Check your external destination — the ticket should arrive as expected.

Miscellaneous

GIF Images Now Retain Their Original Quality

What we fixed: GIF files were getting mangled during upload — the image processor was accidentally stripping the color palette and changing the bit depth, leaving GIFs looking washed out or broken after being attached to feedback items or forum posts.

See it in action:

1. Navigate to a feedback item or forum post where you'd like to include a GIF.

2. Upload or attach your GIF file as usual.

3. View it after saving — it should display with its original colors and animation fully intact. 🎉

Archived Projects Are Now Properly Locked Down

What we fixed: Users on support-level teams were able to sneak into archived projects via a direct link, even if they had zero project roles assigned. They'd show up as "No Teams" in the project summary but could still get in through the back door. Access to archived projects is now correctly enforced.

See it in action:

1. Place a user on a support-level team with no project roles enabled.

2. Archive the project.

3. Have the user try to access the project via a direct link — they should be properly blocked. 🔒

🐞  Bug Fixes 🐞 

Form Engine and Custom Surveys

Survey Element Drag-and-Drop Fixed on Pro Edition Sites

What we fixed: On Pro edition sites, trying to click and drag survey elements in overview mode was throwing a "No access" error and refusing to budge. Elements can now be reordered by dragging them around just like they should be.

See it in action:

1. Open any survey with multiple elements on a Pro edition site

2. Switch to overview mode

3. Click and drag an element to a new position — it moves!

Data Engine and Custom Reports

AI Report Elements No Longer Inherit Instructions From Each Other

What we fixed: When a report contained multiple AI elements, the instructions from earlier elements (like a custom prompt) would bleed into later ones, causing paragraph summaries and other AI elements to follow the wrong structure. Each AI element is now processed independently, so they each respect only their own instructions.

See it in action:

1. Create a report with a custom prompt AI element that has specific formatting instructions

2. Add additional AI elements after it (e.g., paragraph or bullet point summaries)

3. Generate the full report — each element now produces output based solely on its own prompt

🐞  Bug Fixes 🐞 

Data Engine and Custom Reporting

"Is Not One Of" filtering with multiple selections

What we fixed: Fixed an issue where using "Is Not One Of" with multiple selections on a choices element filter would incorrectly show all results instead of excluding the selected options. 

See it in action:

1. Create a filter containing an "Is Not One Of" filter item

2. Select multiple items from the list via ctrl or shift clicking items

3. Your filter will appropriately exclude all items in your filter

🐞  Bug Fixes 🐞 

Data Engine & Custom Reporting

• Report Generation Performance Under Heavy Load

  
  

  What we fixed: When multiple reports were being generated at the same time, things could get a bit sluggish or unreliable. We've made improvements to how reports are processed under heavy load, so your reports should generate more smoothly even during busy periods.

  
  

  See it in action:

  1. Generate reports as you normally would

  2. Even during peak usage times, reports should process reliably

  3. No more wondering if your report got lost in the queue!

Miscellaneous

• Email and PDF Logos Now Display Reliably

  
  

  What we fixed: Some customers were experiencing an intermittent issue where their email and PDF logos would mysteriously stop appearing, requiring a re-upload to fix. We tracked down the root cause and squashed this bug for good. Your branding should now stay put where it belongs!

  NOTE: If a file from prior to this fix is still not working, remove and re-upload it and that will correct it.

  
  

  See it in action:

  1. Navigate to your community theme settings

  2. Confirm your email/PDF logo is uploaded

  3. Send a test email or generate a PDF

  4. Your logo should appear consistently every time (no more disappearing acts!)

🐞  Bug Fixes 🐞 

User Interface and Experience

No More Double Password Error Messages

What we fixed: If your community has a custom password policy set up, users were sometimes getting hit with two error messages at once - yours AND ours. That's confusing and a little annoying, so we fixed it. Now they'll only see your custom message.

See it in action:

1. Go to your Account Settings page

2. Try changing your password to something that doesn't meet the requirements

3. You'll see just the custom error message your admins set up (not a wall of text)

Miscellaneous

More reliable file uploads

What we fixed: Ever try uploading a bunch of files at once and notice some just... didn't make it? Yeah, that was a bug. We've sorted it out so your files actually upload like they're supposed to.

See it in action:

1. Head to any form with a file attachment field

2. Select multiple files to upload at once

3. Watch them all upload successfully (no more mystery failures!)