Backlog Reviews

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.

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.

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.

Backlog offers good value for money with useful features at a reasonable price.

The interface could be more modern and intuitive.

Backlog helps organize tasks and track project progress, making it easier to manage work efficiently.

Backlog is very user-friendly and simple to use. I really enjoy the organizational features for managing different tasks, and I like that I can filter them as needed by status—open, in progress, or closed.

Backlog is great. If possible, I’d love an option to add photos. Sometimes, when there are equipment issues, it would be helpful to see exactly what someone is referring to.

Backlog has helped keep communication clear and organized between staff and management. It’s been super helpful for keeping everyone on the same page.

I find Backlog great for keeping my engineering projects on track by breaking down big goals into bite-size tasks. I love seeing progress visually and moving tasks from 'In Progress' to 'Resolved'. Once a task is in Backlog, I can forget about it, which saves my brain for actual engineering work. I appreciate that Backlog remembers where I stopped, so I don't wonder if I've finished something. I like that when a task is complete or a comment is left, notifications pop up in Slack or Teams. The flat-rate pricing for up to 30 users is fantastic for small groups, and the built-in Wikis and Git repositories are a massive win for engineering projects.

It would be great if there was a 'Simple Mode' that just showed the to-do list and the board until you actually needed the heavy-duty engineering tools. A simplified Kanban board where you only see To-Do, Doing, and Done. No 'Milestones,' 'Categories,' or 'Versions' visible unless you toggle them on.

I use Backlog to keep engineering projects on track by breaking down goals into small tasks. It helps remember tasks for me, freeing my brain for engineering work. Notifications integrate with Slack or Teams, keeping files and chats task-focused, preventing information loss.

I like how Backlog brings clarity, order, and focus to what can otherwise be a chaotic mix of scripts, abstracts, and ideas. It's really helpful to see a list of everything that needs to be done in one visible place. I also appreciate the way it reduces stress and aligns the team by letting everyone see what's coming up next and why it matters. The software helps in keeping the Backlog clean and realistic, which is valuable for maintaining order over time. Its ability to improve collaboration is a major plus.

It's not perfect. Something not working as well could be overwhelming if not cleaned regularly. A backlog can grow too late, turning it into a messy list. It takes significant effort to manage. Prioritization can be challenging, especially when stakeholders have different opinions. There is a lack of visibility for non-team members, making it hard to understand the backlog without explanations.

I use Backlog to keep track of features, additions, and projects, helping decide what to work on next. It prevents scope creep, keeps everything organized, and aligns tasks with business value.

I find Backlog's notification system very helpful, as it sends notifications for every change, making it easy to know the updates happening in assigned tasks. I also appreciate the attachment upload option, which is very useful for filing and fixing bugs and tasks. The ability to manage version control for filed bugs and tasks is a significant advantage, especially with managing Git based on category. When it comes to filing and filtering, the 'me' option is incredibly useful and easily accessible. The initial setup was very simple, and just logging in was sufficient. Overall, Backlog makes it easy to stay informed and manage tasks efficiently.

I find it frustrating that we can only upload one attachment per task, which isn't sufficient. For instance, in tasks where you're filing 3-4 test cases, you're restricted to uploading just one attachment.

I use Backlog for filing and fixing bugs and tasks. It manages version control, is easy for accessing filed tasks, and notifications keep me updated on changes.

I have 2 things I like in backlog. 1st I like how I can see the status of my task when i let my project be test in QA and also the Board helps me to see all pending and in progress task. And 2nd, I like is the connection between backlog and teams, this helps more to track my task status and request help anywhere I go since I can use also my phone. This helps my job work more. Backlog really helps me in work to be more ease and traceable and documented in a second especially when informing the client and same goes to me it works fast and reliable communication tool too when you don't like to interact with people but want to inform them what your task status or where is the status of your request help.

I don't have dislike about backlog since backlog is easily to use and navigate.

Tracking task / request help status - this help me to be track and be informed the status of my tasks after QA. Also the connection between backlog and team, helps me to attend the task easily and solve it quick and make my client happy.

I find Backlog very helpful for tracking the status of unresolved issues and their updates from clients, as well as noting any client remarks. I appreciate how user-friendly and intuitive the UI is, which makes it easy for new users to track and monitor statuses. It's also very convenient that clients and users can register issues with remarks at their own schedule, which helps resolve issues efficiently. The initial setup was straightforward, and around 50 to 60 people use it without any difficulty or gaps in understanding.

As off now there's really nothing which I have encountered to dislike or degrade about this.

Backlog helps me track unresolved issues and their updates from clients, with user-friendly UI. I can monitor issue statuses and root causes, and clients can add remarks. It's easy to use, connecting users and clients flexibly without needing to be online 24/7.

It’s one of the most useful project management tools I use in my business. It allows my clients to add tasks, bugs, and other items without having to rely on email.

So far I haven’t found anything I dislike

It gives me one central place to keep all my client work. My clients can log in at any time and check progress without having to schedule a weekly call just to discuss updates.

It brilliantly merges technical essentials like Git repositories and Wikis directly with task tracking, saving developers from the constant headache of switching between different apps. The automatic Gantt charts are another standout feature, providing a crystal-clear visual of the project’s timeline without requiring any tedious manual setup

Backlog offers limited customization for complex or non-standard project workflows. Large projects can suffer from noticeable performance lag when handling a high volume of tasks. The mobile application is quite restricted and lacks many essential features available on the desktop version. Reporting and analytics tools are relatively basic and lack advanced analytical depth. Finally, the integration library is smaller compared to most major enterprise competitors.

Backlog helps solve the problem of scattered task management and unclear project visibility. By centralizing tasks, discussions, and progress tracking, it allows me to stay organized, prioritize effectively, and collaborate more efficiently with my team. This ultimately improves productivity and ensures that deadlines and project goals are consistently met.