Notifications
Resize the formatting editor in Standard emails and custom messages
What's new: Last week the custom message on notifications picked up formatting. This week it gets some room to breathe. The formatting editor for Standard emails and for custom notification messages (activity announcements and reminders, and phase date changes) used to be stuck at about six lines, so a longer note meant scrolling around inside a tiny box. Now you can resize it vertically, just like the editor for Custom emails.
See it in action:
- From your Surveys, Tasks, Content, or Releases list, use the Notify users action on an item and choose Use custom message.
- Grab the handle at the bottom edge of the editor and drag it down to make the editor taller, or back up to make it shorter.
- Write your note with the whole thing in view. The email your recipients get looks exactly the same either way. 🎉
Good to know:
- The editor resizes up and down only, and it won't go shorter than its starting height.
- Your chosen height isn't saved. The editor returns to its starting size the next time the page loads.
- The resize handle is built for a mouse, so it may not respond to touch.
Content
Every tester gets their own distributed value
What we fixed: Distributed values (the keys or codes you hand out to testers through content) could occasionally go to two testers at once. It happened when lots of testers opened the same content at the same moment, like right after a big invite lands and everyone hits a click-through notice, or when an admin saved the value list while values were being handed out. Not anymore: each value now goes to exactly one tester, or to no more testers than you've allowed with a self-select group's Users per value setting.
See it in action:
- As an admin, add an auto-assign distributed value group to a content item (or notice), paste in your list of keys, and publish it to your testers.
- Have your testers open the content. Each one gets a different key, and it stays the same every time they come back.
- Need to add more keys while testers are already getting theirs? Go for it. Open the group, add to the list, and save. Keys already handed out stay with their testers and never go back into the pool. No more awkward "we both got the same code" emails. 🎉
Good to know:
- If you paste the same key twice in one save, it's only added once. A key that's already in the group isn't added again either.
- Keys that differ only in upper or lower case (like
ABC-1andabc-1) still count as different keys. - Want one key shared by several testers? Use the group's Users per value setting rather than pasting the key multiple times.
- Keys that were already given to two testers before this fix stay where they are. Nobody loses a key they already have.
User Accounts
Alternate names from single sign-on now behave like the rest of your SSO fields
What we fixed: If your site uses alternate first and last names, your sign-in provider can now fill them in for members, the same way it fills email and name. OAuth SSO setups couldn't map those fields at all, and a value set behind the scenes got wiped the next time anyone saved the configuration. On SAML setups, members could edit the alternate names your provider sent, and marking them as required didn't actually do anything. All fixed! 🔒
See it in action:
- Make sure alternate names are on: in your community's User account settings, check Include alternate first & last names.
- Open Single sign-on management and edit your OAuth configuration. You'll now see Alternate first name parameter and Alternate last name parameter, each with its own Identity Provider (IdP) must supply this value checkbox. Fill them in, save, and they stay put, even through later saves.
- Have a member sign in through SSO and open My account settings. Any alternate name your provider sent is locked in place, just like their email and name. Alternate names your provider didn't send stay editable. No more "creative" self-edits to values you rely on. 😉
Good to know:
- If a configuration marks an alternate name as required and your provider doesn't send it, the sign-in stops with a "missing information" message. That's the same thing that happens with a missing first or last name. Heads up for SAML sites: a new SAML configuration has these boxes checked by default, so if your provider doesn't send alternate names, uncheck them or those sign-ins will stop.
- New OAuth configurations also start with both alternate name boxes checked. Uncheck them if your provider won't send these values.
- Alternate name fields only show up in your SSO settings while Include alternate first & last names is on. If you turn it off and then save an OAuth configuration, its alternate name parameters are cleared, so re-enter them after turning the option back on.
See it in action:
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.
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.
See it in action:
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.
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.
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.
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.
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.
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.
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.