🐞  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