21 Backlog Testimonials

"We used to manage and share reports by email, but they would get lost or forgotten. Backlog lets improved how we manage reports for each issue. All reports can now be found in the same project, making them much easier to review."

"Before Backlog, information sharing was difficult. New project members experienced information gaps. After Backlog, people joining in the middle of a project could easily follow progress and get up to speed quicker."

"Backlog makes it easy to tell who’s responsible for what within each project. Many project management tools make it difficult to understand who’s involved in projects, but Backlog makes it simple."

“Backlog is attractive because even members who are inexperienced with this kind of tool can use it easily to collaborate in real time.”

"When managing projects with Backlog, we communicate within issues, so it’s always clear what we’re talking about and who’s involved. This is much more efficient than email."

“Backlog's UI design is very easy to use compared to other task management tools, so I recommend it to those who are not familiar with IT tools.”

“In Backlog, it’s easier to change the task status and status of pull requests, etc. So it saves time as a project manager, and as a developer, it’s easier to use and to learn to use.”

“I felt we needed a tool that was easy to use for everyone in the company and that at the same time would give us the possibility to control and manage our work in one place.”

“We chose Backlog because it’s user-friendly, easy to track multiple projects, and provides Gantt charts and many other features.”

“We saw how our client managed their projects very effectively in Backlog. From then on, we also started using it.”

“They can see how many tasks they have, and as a Manager, I can see who has which tasks, what are they doing, and what will be done next.”

“At that time, I tried to be a kind of bridge between developers and non-developers. But sooner or later, it turned out that I was the bottleneck of the communication. I thought then that we should use the same tool for communication.”

“If I want to present my workload to my managers, it’s very easy. Like, ‘hey this is me, it is full’. There’s a lot of tools like that in Backlog, especially when you look at the Gantt Chart, and the filtering of issues assigned to me.”

“With the Wiki feature, it’s where we store information that is relevant to the specific project. So it’s like documentation for the specific project. We also used Google Docs before but it’s kind of hard to organise the documents there alone.”

“Because Github charges per user, it quickly gets expensive, particularly when we’re working with part-time developers. Github doesn’t differentiate between part-time and full-time users. So this is where the package setup of Backlog was a good aspect for us.”