Centercode Centercode Release Notes logo

Centercode Release Notes

Back to Homepage Subscribe to Updates

Labels

  • All Posts
  • announcements
  • new features
  • security
  • mobile
  • release
  • patch

Jump to Month

  • March 2026
  • February 2026
  • January 2026
  • December 2025
  • November 2025
  • October 2025
  • September 2025
  • August 2025
  • July 2025
  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • October 2020
  • September 2019
  • August 2019
new featuresreleasepatch
3 weeks ago

Weekly Patch and GoEarly Features - February 22, 2026


💡 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. 🔒