You've probably built the same chart more than once. You get a feedback trend or a tuned AI summary looking right in one report, and then you need it in the next one. Until now, that meant rebuilding it by hand and squinting at the original to make sure they match. Starting today, you can pull a finished element in from another report, or duplicate one right where it sits, and spend your time on the parts that are actually new.

#Clone Report Elements Instead of Rebuilding Them

Report elements take real work to get right. You pick the data, build the filter, choose the style, and maybe write an AI prompt worth keeping. Once you've done all that, you shouldn't have to do it twice. Report element cloning gives you two ways to reuse what you've already built.

Clone from another report. When you create a new report element, look for Clone from another report at the top of the element editor. Pick a Source report, then pick the Element to clone, and click Clone this element. The element's whole configuration loads into the editor: its data, its view, its own filter, its style, and any AI prompt settings. Nothing is saved yet. Review it, rename it if you like, and submit it when it looks right. If you back out, the report you're building stays exactly as it was.

Duplicate in place. Want a few variations of the same chart in one report? Hover any element on the Modify this report page and click the clone control next to remove. A copy drops in directly below the original, and everything beneath it moves down one spot. The copy keeps the original's name exactly. We didn't add "(2)" or "Copy of" to the name, because those labels pile up fast once you've made a few copies. Rename it whatever makes sense.

Either way, the copy is its own element from then on. Change it, move it, or remove it, and the original doesn't notice.

A few things to know before you start cloning:

• Same level and same kind. Project reports clone from other reports in the same project, and community reports clone from other community reports. Standard reports clone from standard reports, and API reports from API reports. Cloning between projects isn't supported.
• Only reports you can edit. The source list shows active reports you could already open and modify. If a report isn't in the list, it's archived, the wrong kind, or one you don't have edit access to.
• Report-level filters win. If the report you're cloning into has a report-level filter for that kind of data, the copy uses it. A filter that belonged to the source report's report-level setup stays behind.
• Copies start empty. A cloned element arrives fully configured but shows no data until the report next runs. Refresh the report and your results show up.
• Save before you duplicate. Duplicating reloads the Modify this report page, and any unsaved changes on it, like a half-typed report title, are lost.
• AI elements need AI. Cloning an AI response element requires an active AI data analysis license.
• API access isn't copied. A cloned data package or record lookup element gets its own key and doesn't inherit the original's API access. Grant access to the copy before an outside system can reach it.

For the full walkthrough, see our Guide to cloning report elements.

#Integrations

#Your API key can now tell you which projects it reaches

What's new: Every external API call needs a project key in the URL, but until now there was no way to ask the API which projects a key could actually use. Integrators had to collect each project key by hand and register it on their side every time a new project came along. Now one call returns the whole list. No more copying keys around!

See it in action:

1. Grab an API key you already use for an integration. It needs at least one project-level resource attached, like a feedback type, report, listener, or release type.
2. Make a GET request to /v1/projects on the same external API address you already use, passing your key the usual way (?apiKey=<your key>).
3. You'll get back a projects list, with each project's key (the same identifier used in other API paths), its name, and its status.
4. Attach a resource from a brand-new project to that key and call /v1/projects again. The new project shows up on its own, with nothing to register on the integration's side. 🎉

Good to know:

• You only see what the key can reach. The list includes only projects where the key has a resource attached. It never shows other projects or other communities.
• Closed projects are included. Every project the key reaches is listed, and each one carries a status (such as Active, Closed, or Pending). Integrations should check that field rather than assume every listed project is open.
• Projects without a project key are left out. If an attached project has no project key set, it won't appear in the list. To spot these, open the key's resources list in your community's API keys admin, where those projects are now labeled (no project key) next to their name. Add a project key and the project starts appearing in the list.
• Keys with only community-level resources get an empty list. That's expected, not an error.
• Authentication works the same as before. The call uses the same API key parameter and the same IP allowlist as every other external API endpoint. An invalid key, a missing key, or a call from an IP that isn't allowlisted is rejected the same way.

#Product Versions & Releases

#Publishing releases in big communities works again

What we fixed: In larger communities, the ones with lots of team members and a long history of content views, the Version/Release Preview page could fail with an error. Sometimes the page never loaded at all. When it did load, clicking Publish or Publish and Notify could still fail, so the release never went out. We tracked it down, and the Preview page now loads reliably and publishing finishes, no matter how big your community has grown.

See it in action:

1. Head to Product Versions in your project's admin area, then open an existing Version or create a new one and fill in the required fields.
2. Click Preview. The page should load without complaint, even in your busiest community.
3. Click Publish or Publish and Notify and watch your release go live. No more error pages standing between your participants and the new build. 🎉

Good to know: Nothing about the release itself caused this. It depended entirely on the size and history of the community, which is why smaller communities probably never saw it. If you'd been retrying publishes over and over, you can go ahead normally now.

#User Accounts

#Legitimate users flagged at sign-in can be unlocked for good

What we fixed: Occasionally our sign-in security check flagged a perfectly legitimate user and locked their account. A password reset unlocked it, right up until the next sign-in locked it again. We've added a way to correct these accounts so the lock clears and stays cleared, with no password reset needed.

Good to know: If someone on your team or in your project keeps getting locked out even after a password reset, reach out to our Support team and we'll get it sorted. Their sign-ins are still checked, and too many wrong passwords will still lock the account as usual.

#Signup & Community Setup

#New signups no longer land on a blank template community

What we fixed: A new self-serve signup could end up on a site that technically loaded but showed a sign-in page reading "Sign in to Template Community." No community name, no primary contact, no way in. Behind the scenes, a routine post-release license sync was flipping unclaimed community slots to active before the signup had a chance to set them up, so setup got refused. We've stopped that sync from touching unclaimed slots, and we've added a second safeguard so only a genuine, successful setup can mark a community active.

See it in action:

1. Complete a new signup at signup.centercode.com.
2. Wait for the signup site to hand you off to your new community.
3. Open the domain you requested. You should see your community name, not "Template Community," and the primary contact can sign right in with their access key. 🎉

Good to know: This one mostly bit signups that happened shortly after a release went out. If a brand new site ever came up looking empty or wrong, this was very likely the cause. Any community slots already sitting in that state have been cleaned up as part of the fix.

#Onboarding/Recruiting

#Candidate list uploads with a + in the filename now import fine

What we fixed: Uploading a candidate list to an email-list recruitment invitation would spin forever on Preparing invitations if the file's name happened to contain a + character. No error, no warning, just an endless loader. Renaming the file made it work, but nothing hinted at that. Filenames with a + now import normally.

See it in action:

1. Open a recruitment with an email-list invitation source.
2. Add a new invitation and choose the upload option.
3. Upload a candidate file with a + in the name. Something like tide+list.csv works nicely for this.
4. Watch it sail right past Preparing invitations and finish like any other import. No renaming required. ✅

Good to know: We also made stalled imports fail visibly rather than looping forever. If an import ever does go sideways for a different reason, you'll get told instead of being left watching a spinner.

#User Accounts

#A quick one-time check on your next sign-in

What's new: We've added enhanced back-end security to the platform. Almost all of it runs where you'll never see it, but one part won't: the next time you sign in, you'll pass through a brief account verification screen. It's a one-time step, it only takes a moment, and then you're on your way.

See it in action:

Sign in to your community the way you normally would. A short verification screen appears while we confirm your account. You land on your home page, and you won't see the screen again. 🎉

Good to know:

In the unlikely event the new security measures lock someone out, clearing it works exactly like clearing a wrong-password lockout. A community admin triggers a password reset on the account and the lockout lifts. Our Account management FAQ walks through the steps.

#Onboarding/Recruiting

#Signup verification email now sends again when someone asks for a second one

What we fixed: Someone starts signing up on your community's landing page, asks for a verification email, and then doesn't finish. Maybe a spam filter ate the first email, maybe a corporate proxy blocked the page, maybe they just got pulled into a meeting. When they came back and tried the same address again, they saw the same cheerful "check your email" screen, and no email went out. Not that time, not ever. The only way out was a manager or our engineering team clearing the record by hand. We've fixed the check that was causing it. A candidate who never actually joined your community can now request verification again and get it.

See it in action:

1. Sign out and open your community's landing page.
2. Click Create one, enter an email address that has never been used on this community, then click Verify Email. The confirmation screen appears and the email arrives.
3. Don't finish signing up. Come back a few minutes later and submit that same address again.
4. A second verification email arrives. 🎉

Good to know:

• Resending is rate limited so the form can't be pointed at somebody's inbox as a weapon. There's a five minute pause between sends, and a candidate gets three self-service sends before the allowance runs out. That's three messages spread over at least ten minutes, which is room for a real person to recover and not much use to anyone else.
• Running out is not a lock, and it never needs engineering. The allowance restarts three ways: the candidate clicks a link in any verification email they already have, a manager sends them the invitation from the recruitment pool, or a week goes by. Verification links are good for seven days, and sends older than that stop counting, so a spent allowance recovers on its own even if nobody does anything.
• Most candidates who report being stuck aren't. They have a working verification link sitting in their inbox, and following it both signs them up and clears the allowance.
• A verification email that we accepted and then failed to deliver still counts as one of the three. We know that isn't ideal. The alternative is not counting queued email at all, which is exactly the gap an abuse burst would walk through. Nobody stays stuck: it clears on the same seven day clock, and a manager can release the address immediately.
• Everyone submitting on that page now sees the identical confirmation screen, whether the email sent, was paused, was capped, or the address had already joined. That's deliberate. It means nobody can use your signup form to work out which email addresses belong to your members. The tradeoff is that you can't diagnose a stuck candidate by looking at the page, so go to the recruitment pool instead and check that person's last emailed date.

Releasing a stuck candidate: If someone needs a verification email right now, email them from the recruitment pool. Go to Community Management or Project Management > Recruiting, open Moderate candidates on the relevant recruitment, search for their email address, and use the email action on their row to send the invitation to that one person. Their allowance restarts immediately, and they can submit on the landing page again after five minutes.

One catch worth knowing: it has to be a single send to that one person. The bulk email button at the bottom of the pool, the one that goes to everyone matching your filter, does not restart anyone's allowance, because it doesn't record who it reached individually. Sending from the pool never uses up a candidate's own allowance either, so you can send as freely as you like. It can only help them.

Every project has its own idea of what participants should see first. Some lead with feedback, some with activities, some want a briefing before anything else happens. Until now the platform picked one order and everyone lived with it. Starting today, a project admin drags the sections of Project Home into whatever order fits the program, clicks Save, and every participant sees it that way.

#Drag Your Project Home Into the Order That Fits

The Project Home has always rendered its sections in a fixed sequence we chose. That worked fine until it didn't. A hardware program that ships units wants Activities up top to drive completion. A research team wants Feedback first, because collecting it is the whole point. A project that briefs participants before anything else wants Content leading. One order was never going to serve all three.

The new Project Home Order page lives under Management > Project Configuration. It lists the sections of the Project Home as a vertical drag-and-drop list, each row labeled with its name and a short description. Drag them into the order you want and click Save. There's no save-on-drop here, deliberately, because the change reaches every participant in the project. If you want to start over, Restore default order snaps the list back to the platform default.

Six sections are reorderable: Content, Feedback, Drafts, Surveys, Activities, and Assigned Test Platforms. Release announcements aren't a separate section, so they move wherever Content moves. The Content stream travels as one block, which means individual content items stay in their existing sequence within it.

One saved order applies to everyone in the project, and the same order drives desktop and mobile. Each participant still sees only the sections they're entitled to, arranged the way you set them. Sections with nothing in them keep hiding themselves exactly as they do today, and they hold their configured position for whenever they do have content. You'll never end up with an empty placeholder just because you moved something.

The order is part of project configuration, so it travels on clone. Set it once on a template and every project cloned from that template starts with your layout already in place. That's the fix worth knowing about if your answer to "we don't like the default order" needs to apply to more than one project.

Important note: nothing rearranges on its own. Every existing project keeps rendering exactly as it does today until an admin opens the page and saves a new order. The config page shows your current order as its starting point, so opening it to look around changes nothing. For the full walkthrough, see our Guide to setting your Project Home order.

---

#Product Verification Moves to the Top

Product Verification isn't one of the reorderable sections. It's pinned, and as of this release it's pinned to the top of Project Home rather than sitting below Feedback. If your project uses Product Verification, this is the one thing that looks different on release day without anyone touching a setting. If your project doesn't use it, nothing moves.

The reasoning is straightforward. Product Verification asks participants to confirm they've received the test unit, and it gates their access to activities and feedback until they answer. A question that blocks everything else belongs above everything else.

On the Project Home Order page it appears as a locked row in its fixed position, with a short explanation of why it can't be dragged. We show it rather than hiding it so you can see where your reordered sections land relative to it.

It's worth being clear about one thing: the gate is logical, not positional. Activities stays hidden until a participant answers the product-receipt question, no matter where you put Activities in the order. Reordering changes the visual sequence and nothing else. You can't move a section above or below Product Verification to get around it, and you don't need to worry that dragging Activities somewhere new will open access before a participant has confirmed receipt.

#Integrations

#Finding a Slack channel is now a search box, not a giant list

What's new: Setting up the Slack integration used to load every channel in your workspace into a drop-down before you could pick one. If your workspace has thousands of channels, that meant a long wait, or a page that never finished loading at all. Now you just start typing and we go find the channel for you.

See it in action:

1. Head to your community's Slack integration setup (Community settings > Integrations > Slack).
2. Notice the page loads right away, with no more waiting on the channel list.
3. In Step 2, click the channel box and start typing a channel name. One character is enough to kick off the search.
4. Matching channels appear as you type. Click the one you want, then save.
5. Give Send a test message a try. It uses the same search box, so finding your test channel is just as quick. 🎉

Good to know:

• You need to pick a channel from the search results. Typing something that isn't a real channel won't save, and that's on purpose, so notifications never get pointed at a channel that doesn't exist.
• Changed your mind? There's a small x on the selection to clear it and start over.
• Already had a channel configured? It shows up exactly as you left it. Nothing to redo.
• Your channel list is synced from Slack, so a channel created a few minutes ago might not show up in search yet. If that happens, use the Refresh channels button to pull a fresh list from Slack.
• Big workspaces were the whole point here. 25,000+ channels is no longer a problem.

#User Interface & Experience

#Fold away the survey and feedback groups you're not working in

What's new: Survey and feedback group lists used to show every group fully expanded, every single time, so you'd scroll past three groups you didn't care about to reach the one you did. Now you can collapse a group with a click, and we'll remember which ones you folded. Editing a group has moved to a pencil, so clicking a row is purely for navigating.

See it in action:

1. Open a survey or a feedback type's group list.
2. Click a group's header row. It folds up, hiding its fields. Click it again to unfold it.
3. Fold away everything except the group you're actually working in. Much better.
4. Need to rename a group or change its settings? Hover the group row and click the pencil to open the edit screen.
5. Reload the page, or come back tomorrow, and the groups you folded are still folded, right where you left them. 🎉

Good to know:

• Clicking a group row no longer opens the edit screen. That's the pencil's job now, so editing is a deliberate choice instead of something that happens while you're navigating.
• Your collapsed groups are saved to your account, not your browser, so they follow you from your laptop to any other machine you sign in to.
• It's remembered per individual group, not one on/off switch for the whole list.
• First time in, or nothing saved yet? Everything renders expanded, exactly like before.
• Works the same way in both the survey group list and the feedback group list.

#Onboarding/Recruiting

#Expired invitations on single sign-on communities now lead straight to sign-in

What we fixed: Recruitment invitation links carry a verification window of seven days. Opening one after that window closed, on a community that uses single sign-on (SSO), sent the invitee a fresh verification email whose link landed them on the local account creation form, on a community that doesn't allow local accounts in the first place. Filling it out built a password account with no connection to your identity provider, and when the SSO option's User can upgrade from this field setting was off for email, that person was stuck behind a "one account per email address" error on every attempt afterward. We've routed expired invitations on SSO-only communities straight to SSO sign-in instead.

See it in action:

1. On a community configured for single sign-on only, open a recruitment invitation more than seven days after it was sent.
2. You land on the SSO sign-in entrance right away, with no verification step and no second email.
3. Sign in through your identity provider. Your account is created with its SSO link intact, and the original invitation completes exactly as if it had never expired. 🎉

Good to know:

• Communities using local or hybrid sign-in are unchanged. Invitees still get the verification step and a fresh verification email, exactly as before.
• This covers older links too. If someone re-clicks a verification email that went out before this change, that link now routes to SSO sign-in as well.

#Data Engine & Custom Reports

#Grab your files right from a report

What's new: A file attachment column in a report used to say Has attachment: Yes/No, and that was the whole story. Useful, but it meant opening submissions one at a time, or exporting every file and deleting the ones you didn't want, just to track down a single screenshot. Now you can add a column that shows the actual file names as clickable download links.

See it in action:

1. Open a custom report and edit its columns.
2. Pick a file attachment field, and you'll see a new data point named after it: <field name> files.
3. Add it, save, and run the report. Single files show one filename, and multiple files show them comma-separated, each its own link.
4. Click any filename and the file downloads. That's it, no more ZIP archaeology. 🎉

Good to know:

• Your existing Has attachment: Yes/No columns are completely untouched. This is a new, separately selectable data point sitting alongside it, so nothing you've already built changes.
• It's available in the feedback, user, and project report areas.
• You can filter on it too, with a new File name filter: Contains, Does not contain, Is equal to, Is not equal to, Starts with, and Ends with. There's also Is more than and Is less than if you want to filter by how many files are attached.
• Exports come along for the ride. XLSX gives you real clickable Excel hyperlinks, and PDF shows the filenames as plain text.
• Sign-in is always required to download, in every context, including a link clicked from a distributed or emailed report. Nobody gets file access they didn't already have, and existing file security levels still apply.

#Form Engine & Custom Surveys

#Survey presets show up in an order that makes sense

What we fixed: When you added a survey question from a preset, presets borrowed from other surveys in the same project came through in a seemingly random order. They were actually sorted by a behind-the-scenes name you never see on screen. On top of that, every other survey in the project got dumped into one giant undivided section. We've put presets back in proper question order, and each source survey now gets its own labeled group.

See it in action:

1. Open a project with at least two surveys, where one of them has questions saved as presets.
2. In a different survey, add a new element and open the preset drop-down.
3. Presets from other surveys are now grouped under each survey's own name, listed in the same order the questions appear in that survey. 🎉

Good to know: This is how community question bank presets have always behaved, and project surveys just weren't following the same rule. The difference is most obvious on large projects, where a hefty preset library made the old ordering genuinely painful to work through.

#Form Engine & Custom Surveys

#Completed surveys now show the answer you actually picked

What we fixed: On the review screen for a completed survey, a Choices question set to the vertical radio button style could show the first option as the selected answer, no matter which one was picked. The trigger was oddly specific: it only happened when one of the answer choices had the word "checked" somewhere in its text, like "They matched all the times that I checked today." The review screen was working out which option was selected by scanning for that word, so a choice containing it matched itself and won every time. We've rebuilt how the review screen decides, so it reads the answer that was actually stored.

See it in action:

1. Open a survey with a Choices question using the vertical radio button response style, where at least one choice has the word "checked" in its text.
2. Take the survey and select any option other than the first one.
3. Submit the survey, then view the completed survey review screen.
4. The option you selected is the one looking back at you. 🎉

Good to know: This only ever affected how the review screen displayed the answer. The Data Engine, reporting, and the response edit view had the correct answer the whole time, so nothing you've already collected needs a second look. Horizontal radio buttons had the same quirk, and they're fixed too.

#Conditional questions now stay hidden until the matrix question is answered

What we fixed: When a matrix question included N/A as one of its answer choices, any conditional question tied to that row would show up immediately, before anyone had answered a thing. The row looked untouched, but the conditional logic was reading that untouched row as an N/A selection and firing on page load. We've taught it the difference between a row nobody has answered yet and a real, deliberate N/A.

See it in action:

1. Build a matrix question that includes N/A among its answer choices, such as a 1-5 scale plus N/A.
2. Add a conditional question triggered by N/A on a specific matrix row.
3. Preview or take the survey and leave the matrix question unanswered. The conditional stays out of sight where it belongs.
4. Select N/A on that row and the follow-up appears right on cue. Pick a real score instead and it tucks itself away again. 🎉

Good to know: Reopening a submission that was saved with N/A still shows the conditional on load, which is exactly what should happen: that N/A is a genuine answer. Conditionals on standard choice questions, drop-down lists, and checkboxes all behave the way they always have.

Centralized Jira connections are graduating from GoEarly to production sites. If you've ever configured the same Jira instance across ten different projects, this one's for you. A community admin sets up each Jira instance once, and project admins pick it from a drop-down. Your existing project-level Jira setups keep working exactly as they are.

#One Jira Connection, Every Project That Needs It

Jira credentials used to live inside each project's external destination, per feedback type. Same instance URL, same username, same API token, re-entered for every project that needed it. Rotating a token meant touching each project by hand. Now a community admin configures the Jira instance once in the Integration Center, and every project pointing at that connection inherits the change.

Each connection stores an instance name, a base URL, an authentication scheme (basic with a username and API token, or bearer with a personal access token), and the credentials themselves, encrypted at rest. You can set up as many instances as you need, so an engineering Jira and a support Jira can happily coexist.

Every connection card has a Test button. Select it and we call Jira, then show you the list of Jira projects those credentials can actually reach, 30 at a time. It's a quick confirmation rather than a project browser, and it catches the situation that generates the most support tickets today: a token that authenticates perfectly well but lacks the access the sync needs downstream. A successful test shows a green Connected badge. A failure shows a red Connection unsuccessful with the reason in plain language, like Token expired or Could not reach Jira at this URL. Save credentials without testing them and the card sits at Untested until you do.

Each card also shows a Used by # Centercode projects count that expands into the actual list, so you can see who depends on a connection before you change it. A footnote records who edited the connection last and when. If you remove a connection that's still in use, we tell you how many Centercode projects will break and let you decide whether to continue. Those projects reset to Select and their Jira sync fails on the next attempt, which is the signal for their admins to pick something new.

In a project, the authentication fields on the Jira external destination are replaced by a Connection source drop-down. It lists your community's connections alphabetically, with Project-specific connection at the bottom. Choose a community connection and the instance details display read-only, so you go straight to the JSON mapping without hunting down a token. For a one-off integration, like a contractor's Jira account, choose Project-specific connection and enter the base URL, authentication scheme, and credentials the way you do today.

Switching between the two is safe in both directions. When you move a project from its own credentials to a community connection, the original credentials stay put behind the scenes, obfuscated. If that community connection later disappears, flip back to Project-specific connection and everything you entered is still there waiting.

Important note: Nothing migrates on release day. Every existing Jira external destination lands on Project-specific connection with its current credentials intact, and Project-specific connection isn't going anywhere. Opt in to a community connection on your own schedule, or don't. Your JSON mapping and field configuration behave identically either way. For the full setup walkthrough, see our Guide to Centralized Jira Connetions.

---

#Dynamic Tags Get the Same Picker as Everywhere Else

The old inline drop-down for inserting dynamic tags into the JSON editor is retired. The dynamic tag button now opens the same search modal you already use elsewhere in the platform. Park your cursor in the JSON, open the modal, add the tags you need, close it, then move them where they belong.

Dynamic tags are a one-and-done setup task, so the extra click buys you a picker that works the same way everywhere.

#Onboarding/Recruiting

#Joining a project with SSO now works from long recruitment links

What we fixed: If you had a URL recruitment set up and someone signed in with SSO right from that recruitment page, they'd get bounced to our "no page exists at your destination address" error page instead of being joined to the project. Not exactly the warm welcome we were going for. Behind the scenes, the link they were sent to after signing in wasn't being recognized properly because of its length, so the whole join stalled out before the application survey ever loaded. We've corrected the routing, so those links resolve the way they should have all along.

See it in action:

1. Head to a project with a URL recruitment set up with a key over 40 characters, the kind with a custom link like yoursite.com/your-recruitment-name.
2. Open that recruitment link in a fresh browser, or an incognito window, so you're starting signed out.
3. Sign in using SSO from the recruitment page.
4. You'll land right where you should, moving into the project's application survey instead of an error page. 🎉

Good to know: This showed up most often on recruitments with longer, multi-word keys, but the fix covers all of them. If anyone reported a "bomb error" when trying to join through a recruitment link, this was almost certainly the culprit, and it's worth letting them know they can try again.

#Your "send without an opportunity link" confirmation now sticks

What we fixed: When you send a recruitment email that uses the %OPPORTUNITYURL% tag, you have to check Allow email to send without an opportunity link to move forward. Trouble was, if you then hit the recipient-count validation error on the preview page, that checkbox quietly forgot you'd ever confirmed it. You'd fix the recipient count, hit send again, and get blocked by an opportunity-link error, with no way forward except backing up a page and re-checking the box. We've fixed that, so your confirmation carries through.

See it in action:

1. Create or open a recruitment email that uses the %OPPORTUNITYURL% tag with a custom footer.
2. Check Allow email to send without an opportunity link and continue to the preview page.
3. Click send without confirming your recipient count first, so you trigger the validation error on purpose. (Yes, we're asking you to break it. Live a little.)
4. Now confirm your recipient count and send again. It goes through, with no second detour back to re-check that box. 🎉

Good to know: Nothing about how the email itself sends has changed here. This is purely about the confirmation sticking around so you're not stuck in a loop on the preview page.

#Integrations

#App store release automation now runs again

What we fixed: If you had TestFlight or Google Play automation set up, it could quietly refuse to do its job: either stalling out behind the scenes, or never kicking off at all while the settings screen happily showed it as enabled. We've fixed the setting it was misreading, so automation now runs when it says it's on.

See it in action:

1. Head to Community > Integrations and open your TestFlight or Google Play integration.
2. Check the linked projects list to confirm your project is connected and automation is switched on.
3. Push a new build up to the store, then pop over to the integration's log.
4. You should see the build get picked up and processed, with no mystery silence. 🎉

Good to know: The sneakier version of this one left no trace at all. Automation simply never started, with nothing in the log to explain why. If you'd given up on an automation setup because it seemed to do nothing, it's worth another look.

#Webhook macros that pull in outside data no longer crash

What we fixed: Running a data-pull webhook macro (a Salesforce lookup, for example) could fall over if the other system came back with nothing at all. From a user's User Summary page you'd get a script error, and from User Management the progress bar would just spin forever without ever telling you why. We now handle those responses gracefully.

See it in action:

1. Open any user's User Summary page in a community that has a webhook macro configured.
2. Click the macro from the left-hand macro links and run it.
3. It completes cleanly, with no error popup this time.
4. Try the same macro from User Management. The progress bar actually finishes instead of spinning into eternity. 🎉

Good to know: If the external system genuinely does return nothing, the macro now fails cleanly with a visible error rather than taking the whole run down with it, so there's something concrete to look at instead of a silent hang.

#Test Planning

#Product Verification Stays Published Like It Should

What we fixed: Product Verification was quietly flipping to an unpublished state after an admin opened one of its associated macros and came back. Since Product Verification acts as a hard gate, that meant everyone in the trial got stuck until someone noticed and republished it. We fixed it so Product Verification holds its published state.

See it in action:

1. Open a project with Product Verification published and gating trial access.
2. Click into one of its associated macros, then head back to the Product Verification page.
3. Product Verification is still published, right where you left it. 🎉

Good to know: Product Verification now only unpublishes when you choose to do so yourself.

#Email

#Large Email Resends No Longer Hit an Error

What we fixed: Resending a big batch of community-level email at once (think 100 at a time) could throw a server error. We fixed it so large batches go through without a hitch.

See it in action:

1. Head to a community-level email with a hefty queue.
2. Resend a large batch, for example 100 recipients.
3. It sends without a hitch, no need to break it into smaller chunks. 🎉

#Form Engine & Custom Surveys

#AI-Generated Surveys Point Conditionals at the Right Question

What we fixed: When AI built or imported a survey with conditional logic, the branching rules landed on the wrong question, consistently one spot off. That meant admins had to fix each one by hand. We tightened up the logic so conditionals now point to the question they were actually meant for.

See it in action:

1. Use AI survey creation to generate a survey that includes conditional (display or branching) logic.
2. Review each conditional against your element list.
3. Everything points where it should, no manual cleanup needed. 🎉

Good to know: We also tightened up how character limits are handled during AI survey creation as part of this fix.

#Feedback

#Summary Prompt Enhancements No Longer Disable AI Reply Generation

What we fixed: Adding a prompt enhancement to summary generation had a side effect: it switched off AI reply generation and wiped out its custom prompt. We fixed it so these two settings stay independent of each other.

See it in action:

1. Turn on both AI reply generation and summary generation in Feedback collaboration.
2. Add a prompt enhancement to summary generation.
3. Your AI reply generation setting and its custom prompt stay exactly as you left them. 🎉

#AI-Enhanced Feedback Keeps Its Formatting

What we fixed: When AI enhancement ran on a multi-line or rich-text feedback element, the enhanced version flattened everything into one run-on paragraph, losing line breaks and italics. We fixed it so the enhanced view keeps the structure the original author intended.

See it in action:

1. Open a feedback item with AI enhancement enabled on a rich-text element that has line breaks and italics.
2. Toggle to the AI-enhanced version.
3. Line breaks stay as separate lines and italics stay italic. 🎉

#Onboarding/Recruiting

#Revoke Pending Invitations Through the Onboarding API

What we fixed: The onboarding (user import) API only worked one way. You could push users into a pool, but there was no way to pull an unused invitation back out without going into the platform directly. We added a revoke counterpart to the add endpoint, so integrations can cancel a pending invitation programmatically.

See it in action:

1. Add a user to an onboarding pool via the API, as you do today.
2. Call the new revoke endpoint with the same email you used to add them.
3. That pending invitation can no longer be consumed. The person only gets back in through a fresh invitation. 🎉

Good to know: This only affects pending invitations, anyone who already joined is unaffected. The revoke endpoint requires the encoded email as a parameter to succeed.

#Data Engine & Custom Reports

#SSO Source and Integration ID Line Up in Reports

What we fixed: In custom reports, the SSO source and SSO integration ID columns sorted their multi-value entries in different orders, making it tricky to tell which ID matched which source. We fixed it so both columns order their entries the same way.

See it in action:

1. Create a custom report showing SSO source and SSO integration ID.
2. Check a member with more than one SSO source.
3. The sources and their IDs line up in the same order across both columns. 🎉

#User Accounts

#SSO sign-in now works even when your login provider skips the email

What we fixed: If you invited someone to a project and they signed in through SSO, they could get stuck at the door when their identity provider didn't hand over an email address. Even when their real email matched the one you invited, Centercode had nothing to match it against, so they were left standing on the welcome mat. We taught Centercode to reconcile the invite's email with the authenticated SSO identity, so these folks can sail right through.

See it in action:

1. Invite a user to a project by their email address.
2. Have them sign in through your SSO provider, even one that doesn't return an email in its response.
3. They complete sign-in and land in the project. No more dead ends! 🎉

Good to know: This was a rare edge case, but a total roadblock when it hit. Affected invitees had no way in, and there was no workaround on our side. If your identity provider keeps email addresses close to the vest, you're covered now.

#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. 🎉

Summer's here, and so is a release we've been looking forward to. The headliner is Required on Duplicate, graduating to live servers after its run on GoEarly. Duplicates used to be a mechanism for exclusively adding weight to existing feedback. Now they can carry real context forward into your views, reporting, and exports. Over on GoEarly, we're previewing Centralized Jira Integration, which lets you set up your Jira connections once at the community level and share them across projects. Before we get into the features, though, here's a change behind the scenes that we're genuinely excited about.

#An exciting change in how we ship

We've changed how we build and deliver Centercode behind the scenes, and it's a change we're excited about, because you're the one who benefits. What it means for you: we can get new capabilities into your hands sooner, react faster when you need something adjusted, and roll out improvements without interrupting your work. It's the kind of thing you'll feel more and more as we go.

#✨ New Features ✨

#Required on Duplicate

When a participant runs into something another participant already reported, they have two quick ways to say "me too": voting on an existing issue, or matching a predictive suggestion as they submit. Both paths used to do the same thing behind the scenes. They added one to a counter. You knew more people hit the issue, but not what was different about each encounter: their device, their build, the time it happened, the steps that led there.

Required on Duplicate closes that gap. You can now flag specific form elements as required on duplicate, so that when a participant claims an existing issue, they're prompted to fill in just those fields before the duplicate is recorded. A focused popup appears with only the fields you've marked, nothing else, so it stays quick for the participant while capturing what your team actually needs to triage.

That captured context travels with the duplicate. Each "me too" now creates a real duplicate submission, linked to the original, with the participant's data attached. From there it flows into your comparison view, reporting, and exports, the same as any other feedback. You're triaging from what people actually reported, not from a count and a guess.

Setting it up is per element and entirely up to you. Inside a feedback type, open the form element you want to collect on a duplicate and turn on required on duplicate. Good candidates are short, high-signal fields like time, device, build, and steps to reproduce. Eligible field types include text inputs, date and time pickers, single and multi-select drop-downs, and rating elements. File uploads, AI-enhanced fields, and read-only elements stay out of the duplicate flow to keep the popup fast. If a participant cancels the popup, no duplicate is recorded, so only complete submissions count.

A few things worth knowing. Duplicates collected before you turned the setting on will show blanks for those fields, since the data wasn't requested at the time. The same participant can log more than one occurrence on the same issue, which is intentional. And if you ever remove a duplicate relationship, the context you collected stays put. Read more here!

#💡 GoEarly Features 💡

#Centralized Jira Integration

If you run Jira integrations across more than a couple of projects, you know the drill. Every project, every feedback type, the same credentials maintained by hand. When an access token expires, you go update them one at a time, and there's no single place to see which projects share a connection or whether a key still has access.

Centralized Jira Integration, now previewing on GoEarly, lets you manage your Jira connections once at the community level instead of project by project. Set up a connection a single time, with its name, base URL, authentication type, and credentials, and share it everywhere it's needed. Each connection shows which projects rely on it and when it was last edited, so you finally have a clear picture of what's connected to what.

Project-level destinations gain a connection-source choice. Point a destination at a shared community connection, or keep using project-specific credentials exactly as you do today. Nothing about your existing setups changes unless you decide to move them, and your credentials are preserved through every step: switching to a shared connection, having one removed, and recovering.

Our favorite part is the built-in Test action. It checks a connection and shows you which Jira projects it can actually reach, which catches the most common snag we see in support: a key that connects just fine but quietly lacks access to the project you're aiming at. Instead of guessing, you get a straight answer.

Want a first look? Sign up for GoEarly now!

#Feedback Workflows

#Notify new owner emails now reach the whole team

What we fixed: When feedback ownership moved to a team, the Notify new owner email could quietly skip some members. If one person on the team had opted out of unessential email, everyone listed after them was dropped and never got the notification. We rebuilt the recipient logic so that only the person who opted out is skipped. Everyone else on the team gets the email as expected.

See it in action:

1. Set up a feedback workflow that notifies a new owner, with a team as the new owner.
2. Have one member of that team opt out of unessential email.
3. Trigger the ownership change and confirm every eligible team member receives the notification. 🎉

#Integrations

#Mapping users to Jira fields now works reliably

What we fixed: Sending feedback to Jira could fail when a user field like Reporter or Assignee was mapped. The Insert JSON data helper was building those fields in a format modern Jira Cloud no longer accepts, so Jira rejected the affected tickets. We updated the helper to use the account-based format Jira now requires, and the fix covers Reporter, Assignee, and any user-type custom field.

Good to know: User fields in Jira are identified by account ID, so you'll need to grab the account ID from Jira and drop it in where the tag or placeholder would normally go. Our Jira integration FAQ walks through where to find it.

#Data Engine & Custom Reports

#Custom reports can now include duplicate feedback

What we fixed: Custom reports built on a feedback data source left duplicate submissions out, so there was no clean way to roll them into your reporting. We added an Include duplicates option to feedback report elements, so you can choose to fold duplicate feedback into a report alongside everything else.

See it in action:

1. Open a custom report and add or edit a feedback element built on a feedback data source.
2. Enable Include duplicates.
3. Save the report and confirm duplicate feedback is now included. 🎉

Good to know: The option lives on the individual report element, so you can include duplicates in one element while leaving the others as they are.

#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. 🎉

#New Features

#Embed Interactive HTML Prototypes Right in Your Content

What we fixed: Want to drop a self-contained HTML prototype into your content? You can now upload it as an External Embed asset and reference it inline, and it'll render in its own isolated frame. No more crashes on save or rendering hiccups from pasting big chunks of prototype HTML into the content body.

See it in action:

1. Head to the External Embed header-assets block and upload your HTML file.
2. Reference it inline in your embed code.
3. Publish and watch your prototype come to life in a tidy, sandboxed frame. 🎉

Good to know: This works best with a single self-contained file. A split HTML + CSS + JS set won't resolve its relative links, so bundle it all into one file for the smoothest results.

#Feedback

#Your Display Name Stays Your Display Name in AI Summaries

What we fixed: When the AI summarized a feedback discussion, it was sometimes calling participants by their real first name (pulled from their profile) instead of the display name shown right there on the ticket. A little confusing, and not great for folks who set a display name specifically to control how they show up. We tracked it down to the summary reading names straight from the user profile and rebuilt it to respect the ticket. AI summaries now stick to the display name, just like the rest of the platform.

See it in action:

1. Open a feedback ticket where the original poster has a display name that's different from their profile first name.
2. Generate the AI summary on the discussion.
3. Check the name in the summary. It'll match the display name on the ticket, no surprises.

Good to know: This keeps name-masking consistent everywhere, so participants always show up the way they expect to.

#Data Engine & Custom Reports

#Excel Exports No Longer Trip Over Long Element Names

What we fixed: Excel caps sheet names at 31 characters, so we shorten long report element names to fit on export. If that shortened name happened to land on a character Excel doesn't allow at the end (an apostrophe, for example), the whole export would fall over. We've smoothed that out, so long names won't break your export anymore.

See it in action:

1. Build a report with an element that has a long name (bonus points for one with an apostrophe right around the 31st character).
2. Export to Excel.
3. Watch it export cleanly instead of throwing an error. 🎉

#Integrations

#Email Jira Links Now Match Your In-Site Links

What we fixed: If you set up a custom Public Link Base URL for an external Jira destination, the in-site "pill" links used it, but the "Jira link" dynamic tag in workflow and feedback macro emails was still pointing at the original Jira URL. The same record could send people to two different places depending on whether they clicked in-site or in an email. Now both surfaces use the same configured URL.

See it in action:

1. In an external Jira destination, set a Public Link Base URL that's different from the technical base URL.
2. Check the Jira "pill" link on a feedback record in-site.
3. Trigger a workflow or macro email with the "Jira link" dynamic tag for the same record. The email link now matches the in-site one.