Centercode Release Notes
Back to all updates

Weekly Patch - June 21, 2026

by Tony Fisher
Fixes

Feedback

Workflow changes now save reliably on large team projects

What we fixed: On projects with a lot of teams, saving a change to a feedback workflow could fail with an error and refuse to go through. The workflow page was sending far more data than it needed on every save, and past a certain team count that payload got large enough to be rejected before the save could even run. We rebuilt the save so it only sends what it actually needs, which means changes go through cleanly now even on the most team-heavy projects.

See it in action:

  1. Open a project with a large team structure and go to its feedback workflow settings.
  2. Edit a workflow step. For example, set a state to allow New with no team change.
  3. Save the change and it goes through without an error. 🎉

Good to know: This also makes the workflow configuration screen a little snappier, since there's less data moving back and forth behind the scenes.

Feedback recommendations stay hidden when a type isn't accessible

What we fixed: When a feedback type was turned off for everyone, the recommendation lightbox and its link could still appear, and selecting that link sent participants to an access-denied page. We updated the prompt so it checks whether the participant can actually submit to the linked type first. If they can't, the prompt stays hidden and no one lands on a dead end.

See it in action:

  1. Set a feedback type's access to off for all users.
  2. As a participant, go through the flow where the recommendation lightbox would normally appear.
  3. Confirm the lightbox and its link no longer show, so there's no access error. 🎉

Integrations

Removing a macro or listener now clears the External Data fields it created

What we fixed: When you removed a Webhook macro or an External destination listener, the External Data fields it had created were left behind. Those orphaned fields still showed up as view columns and dynamic tags, with no way to clean them up on your own. Removing the macro or listener now also removes the External Data fields it created, so they no longer linger in your views or tag pickers.

See it in action:

  1. Create a macro with a webhook and data return that produces an External Data field, then run it once so the field appears.
  2. Remove the macro.
  3. Open a view or the dynamic tag picker and confirm the leftover field is gone. 🎉

Good to know: This kind of cleanup used to require a request to our team. It happens on its own now.

Failed Jira pushes now show a clear error instead of staying pending

What we fixed: When a push of feedback to Jira failed, the tag stayed on Pending indefinitely, so there was no easy way to tell the push had actually failed. Failed pushes now move into a clear error state that links straight to the integration log, so admins can open it and diagnose what went wrong. Pending still shows while a push is in progress and updates on its own once the Jira issue is created.

See it in action:

  1. As an admin, open a feedback ticket whose Jira push has failed.
  2. Notice the tag now shows a clear error state instead of Pending.
  3. Select the error to open the integration log and diagnose the issue. 🎉

Good to know: This error state is admin-only. If you display Jira tags to participants, they'll only ever see a resolved link, never a pending or errored one.

Data Engine & Custom Reports

External Data filters now include records with no value

What we fixed: The Is not equal to and Does not contain filters on External Data fields were skipping records that had no value for that field. Because an empty field has nothing to compare against, those records were dropped from the results, which in some cases made the filters return nothing at all. We corrected the comparison so an empty value now counts as not equal to and does not contain, and those records show up where you'd expect.

See it in action:

  1. Open a User or Feedback view in a project with an External Data field that's empty on most records.
  2. Add a filter on that field using Is not equal to or Does not contain.
  3. Confirm records with no value for the field now appear in the results. 🎉