Centercode Release Notes
Back to all updates

Weekly Patch - July 7, 2026

by Tony Fisher
Fixes

User Agreements

Signed agreements now get their PDF copies

What we fixed: If your community uses a custom primary domain (your own branded URL), signed user agreements weren't generating downloadable PDF copies. This meant the PDF and Download all agreements buttons went missing entirely. We tracked the cause to how the archiving job builds its capture URL, and agreements now get properly archived no matter what domain you're on.

See it in action:

  1. Go to Community > Agreement center and search for a user who has signed an agreement.
  2. Hover over their agreement row. The PDF button is back where it belongs.
  3. Open the agreement and you'll find Download as PDF at the bottom, plus Download all agreements ready to go. 🎉

Good to know: Agreements that failed to snapshot before this fix will need a backfill on our end to catch up. Reach out if you're missing older PDFs and we'll get them regenerated.

Integrations

Jira pending status now checks the right team

What we fixed: Feedback tickets sometimes showed a "Jira pending" status when they shouldn't have. If one team had a Jira external destination set up on a status, another team using that same status got tagged as pending too, even without any Jira integration of its own. We updated the check to pay attention to which team is actually involved.

See it in action:

  1. Set up a Jira external destination on one team's status (say, your PM team's New).
  2. Have a different team's matching status (like a participant New) route normally, with no external destination.
  3. Submit a new ticket and view it. The status stays clean, with no stray "Jira pending" tag where it doesn't belong. 🎉

Slack stops double-posting your feedback

What we fixed: When AI feedback features were switched on, Slack notifications fired again every time a feedback item was edited or had its status changed, not just on the original submission. We applied the same one-and-done guard the standard path already used, so Slack posts exactly once.

See it in action:

  1. On a project with Slack integration and AI feedback summaries active, submit a new feedback ticket.
  2. Watch your Slack channel light up with the one post you'd expect. 🎉
  3. Reopen that ticket, change its status, and save. Your Slack channel stays quiet.

Feedback

Impact score widget text stays visible on light themes

What we fixed: On the feedback view, the impact score widget's project points, community points, and user name borrowed the Text links and header buttons theme color. If that color happened to be white or close to it, the text turned white-on-white and disappeared. Those values now use the same readable color as links inside a feedback description, no matter your theme.

See it in action:

  1. Set your theme's Text links and header buttons color to white or something very light.
  2. Open a feedback item and look at the impact score widget.
  3. Project points, community points, and the user's name are all clearly visible. 🎉