G2

Phil J.

Product and Growth Lead

Computer Software

Mid-Market (51-1000 emp.)

6/24/2026

"I've found something much more useful than just a project management tool"

5/5

What do you like best about Backlog?

One of the first things I appreciated was having tasks, bugs, and code connected in the same place. Being able to link commits, pull requests, and issues without constantly jumping between different tools ended up being more valuable than I expected. There were plenty of times when I needed to understand why a change had been made weeks earlier, and I could go from the task straight to the related code in just a few clicks. The Gantt Charts, Kanban Boards, and Burndown Charts also surprised me in a good way. Not because they're the most advanced features on the market, but because they fit naturally into the workflow. Another thing I discovered recently is the new Backlog AI Assistant. I originally tried it out of curiosity, assuming it would be just another AI feature added because everyone is doing AI now, but I ended up using it to summarize activity, organize scattered information, and get a quick overview of project status without manually digging through the entire history. Review collected by and hosted on G2.com.

What do you dislike about Backlog?

The mobile app is perfectly fine for checking updates or replying to comments, but when I tried managing more complex tasks from my phone, I quickly found myself wishing I was back at my desk. It gets the job done, but it's clearly not where Backlog shows off its best side. That said, one thing I have to give it credit for is reliability. I've never run into any major stability issues or had one of those moments where the platform made me question whether I could trust it. It may not be perfect everywhere, but it's always been dependable when I need it. Review collected by and hosted on G2.com.

What problems is Backlog solving and how is that benefiting you?

A moment when a customer reported that a function was no longer behaving as expected; the fun part was that technically the system was functioning exactly as it had been programmed but the real problem was that nobody could remember when that behavior had changed. We started the usual round of questions: "Did you make that change?" " This came from a meeting? " Was it a client request or an internal decision?" No one really knew. The interesting thing is that every response ended up inside Backlog. We found a task that had been created months before, the change discussion, customer feedback, final approval and even related commits. There was no conjecture. Since then, I’ve started to look at the Backlog differently. I stopped seeing it as a simple task manager and started treating it more like a living story of the project. In fact, more than once I’ve gone back over old decisions before starting a new feature, just to understand what problems we had tried to solve in the past. Review collected by and hosted on G2.com.