The Stories list is the heart of your project in Backlogic—this is where everything comes together. From capturing ideas to refining requirements and tracking progress, this is where work gets structured, prioritized, and executed.
To help you get the most out of it, Backlogic provides several views, each designed for a specific purpose. Let’s take a closer look.
Before diving into the views, let’s clarify the three story types used across all views:
Now, let’s explore the different views and how they help you manage your project efficiently.
The Tree View reveals the hierarchy between items in your backlog. Unlike many other tools, Backlogic lets you nest items as deep as needed:
• Stories can contain Tasks or Bugs
• Tasks can contain other Tasks
• Bugs can only contain Bugs or Tasks
Why It’s Useful
• Visualize your project’s structure—see the relationship between Stories, Tasks, and Bugs.
• Get a mental model of your project’s outcome and current state.
• See what’s being built (Stories), what needs to be done (Tasks), and what issues need fixing (Bugs).
• No need for redundant descriptions—items are placed in their natural context.
You can view an item’s context either in its card or in its detail view. The item’s hierarchy appears above its name, giving you instant bearings. Clicking on the path takes you to its parent. Similarly, if the item has children, they are displayed beneath its name for quick navigation.
The Planning View helps you organize work across your backlog and sprints.
• Drag items from the backlog into a sprint manually
• Use Backlogic’s automated tools to schedule items into the first available sprint
• Balance workload distribution effortlessly
Why It’s Useful
• Quickly assign work to upcoming sprints.
• Adapt plans effortlessly—as estimations change, let Backlogic automatically reschedule with a single click.
• Get a realistic timeline—see what to expect and when, based on actual data.
The Kanban View is the classic swimlane-based board that shows the status of your items at a glance.
• See work progress from To Do → In Progress → Done
• Drag and drop items between lanes
• Adapt workflow stages to fit your process
Why It’s Useful
• Provides a real-time overview of work in progress.
• Helps teams quickly identify bottlenecks.
• Ideal for teams working in continuous delivery.
The Burndown View displays the well-known burndown chart, showing how work is progressing over time.
• Track how many tasks remain vs. expected completion
• Identify whether work is ahead, on track, or falling behind
• Adjust workload based on velocity trends
Why It’s Useful
• Helps with sprint and release planning.
• Makes project progress quantifiable and predictable.
• Encourages data-driven decision-making.
The Archive View holds items that have been marked for deletion before they are permanently removed from the system after 30 days.
• Review and restore deleted items if needed
• Keep a clean backlog without losing track of removed items
Why It’s Useful
• Prevents accidental permanent deletions.
• Gives teams a buffer period to recover removed work.
• Keeps the system clean without immediate data loss.
Summarising the views, if you need to
Traditional project management tools work if your team has great discipline in every situation and time on their hands. If only that were true…
Well-defined user stories are essential for Agile development. Let’s explore why, common challenges, best practices, and how to write better stories
A project in Backlogic is built around a set of lists—each serving a specific purpose. But what exactly are these, and how do they help?