Real feedback from real teams shapes better software. Over the past year, we went deep with CTOs, developers, product managers, and team leads who build on Assembla every day. Their input drove this release and it’s shaping everything we’re building next. Here’s the full picture.

What Assembla users have been telling us: the full picture

“

It just works. Of all the ticketing tools I’ve used in decades of work, it’s the one I’ve actually been most impressed with, to be honest.

[Yorick Phoenix,] CTO, Issio Solutions, Inc · 12 years with Assembla

“

A small player in the space, kind of outdated. We’ve had to do a lot of work to make it work for us.

[Jim Edelstein,] Director of Engineering, Platphorm LLC · 8 years with Assembla

Two customers. Both long-term. Both telling it straight. Assembla’s reliability and workflow depth earned that first quote over twenty years. This release closes the interface gap that drives the second.


Assembla user feedback: what’s working and what isn’t

Across interviews, NPS responses, and in-product surveys, the same themes surfaced regardless of team size, industry, or how long someone had been building on the platform.

The details that matter most

The feedback didn’t stay at surface level. One user had already written a custom CSS override to fix the comment textarea height. Another flagged dark mode rendering problems in git diffs. A third pointed out that clicking a ticket description to copy text triggers edit mode: small on its own, but it compounds across a full working day.

That level of specificity is what makes customer feedback genuinely useful. We built the fix list directly from it.


What changed in Assembla’s interface and usability in 2025

This release is a focused modernisation, not a full platform rebuild, and we’re not framing it as one. We refreshed the visual foundation, cleared a significant bug backlog, and sharpened the areas of daily usability where friction had built up. Here’s what changed in practice.

A fresher interface

Typography, spacing, colours, layout: all updated across the platform. The interface now looks like 2026, not 2012. If you’ve been reluctant to open Assembla on a screen share, that specific friction is gone. Dark mode ships properly implemented, not bolted on as an afterthought. Whether your teams manage SVN repositories, Perforce, or Git, the surface they work in every day is cleaner and more consistent.


Bug fixes: a significant backlog

Since 2024, we’ve worked through a substantial list of issues customers flagged in interviews and surveys: slowdowns, inconsistent rendering, interactions that misbehaved under pressure. Unglamorous work, but the kind that compounds. Every fix removes a friction point your team was working around without knowing it.


Search improvements

Search now works the way it should. We resolved the 404 errors and missing results that were eroding trust in search. There’s still room to improve, and we will.


What we’re focused on next

ON OUR ROADMAP
Code review and merge request workflows. Stronger MR workflows, better diff readability, a Git code review experience that maintains pace with how modern teams actually ship. This is where our next meaningful investment is going.
The comment editor. Markdown support, resizable input, and proper quote formatting. The current editor has served its time. A serious upgrade is next.
Click-to-edit on ticket descriptions. Read mode and edit mode need to be clearly separated. It’s a targeted fix with an outsized impact on daily use, and it’s on the list.
Filtering and advanced search. Dynamic filtering and custom query capabilities are coming. What shipped in this release is the foundation. We’re building on it.

No false timelines. We ship when it’s right, and we’ll keep you notified when it is.


Switching to Assembla’s new interface before July: what to expect

If you’re still on the old interface, the move to the new one happens before July. Transitions create adjustment: muscle memory breaks, layout shifts. That’s normal.
What’s stayed the same: every workflow, ticket, integration, and data point your team depends on. The underlying platform hasn’t changed. The surface has.
Give the new interface a week of real use before drawing conclusions. If something actively gets in your way, tell us. All feedback from this release is already shaping what we build next.

Why Assembla is investing in usability and why we’re being public about it

Investing in a platform means more than shipping features. It means listening carefully, fixing what slows teams down, and being transparent about the direction ahead. That’s the work.

Assembla is moving. The bugs that ground people down in 2024 and 2025 are mostly resolved. The interface reflects 2026, not a decade ago. And the roadmap is the most concrete it’s been in years, because the feedback which shaped it was the most specific we’ve ever received.

Teams that have built on Assembla for years deserve a straight account of the current situation. Not a press release, not a feature announcement. This is that account, and there’s more coming.


Try Assembla’s updated platform or come back for a look

CURRENT USERS

Your workflows, your data, your integrations — all exactly where you left them. The surface has changed.

Explore the new UI →
BEEN AWAY FOR A WHILE?

Things have changed, enough that it’s worth another look. No credit card required.

Start a free trial→
HAVE FEEDBACK?

Every response reaches the team. Your input shapes what we ship next.

Tell us what you think →