The backlog is the Goals workspace for worthwhile work that is not ready to occupy the active board. It lets a space keep promising ideas, paused efforts, and later priorities without mixing them into the work people are trying to move forward now.
A backlog goal is still a complete goal. Moving it away from the board changes its placement, not its identity or the context people have already built around it.
Keep Future Work Without Losing Its Story
The backlog is more than a list of card titles. Each goal remains connected to its article, reference, activity, status, assignee, and color tag. Comments and other article content stay with it as well. Someone can open a backlog row in the goal details panel, read the full background, and return to the same planning view.
This makes the backlog useful for work that deserves to survive but would distract from the current workflow. A goal can wait there while its scope is clarified, while the right contributor is found, or until the space is ready to make it active.
Backlog does not mean deleted, completed, or private. The goal keeps following the visibility rules of its space and activity. Its existing link and reference, such as VS-42, continue to identify the same goal.
Read The Backlog At A Glance
The Backlog heading shows how many goals belong to the current area and filter selection. Long backlogs load progressively as you scroll, so you can see the overall size without waiting for every row to appear at once.
Each loaded row brings the most useful planning context into one compact line:
The backlog keeps its total and the most useful planning details visible while future work stays outside the active board.
Select the row when the short summary is not enough. The goal opens beside the planning surface, preserving the board position, filters, search, and backlog state you were using.
!VS-10 Whiteboard performance cleanups open beside the Social Media For Innovation backlog with its activity, prepared status, assignee, and reporter visible
Opening a backlog row reveals the goal's full document while preserving the backlog view behind it.
Prepared Status Keeps The Next Move Clear
A goal keeps a workflow status while it waits in the backlog, even though it is not currently shown in that board column. This prepared status answers a practical question: where should the goal re-enter active work?
For example, a goal can wait in the backlog with To Do prepared, then return to that column when the team is ready. An editor can change the prepared status directly from the row without first moving the goal onto the board.
If a prepared column no longer exists, Visual Space uses the board's starting column or another available column. The goal is not stranded by a later workflow change.
Refine A Goal Where It Waits
People with access to edit a particular goal can rename it and change its prepared status from the backlog. The row also supports quick planning changes without requiring the full article to be opened:
These compact controls are useful for triage. The article remains the right place for the fuller explanation, supporting material, and discussion that help a contributor understand why the goal matters.
Space owners and goal managers with coordinator access can also create a published goal directly in the backlog. A title is enough to start. They can add it at the end or at an available position between rows, then develop its article through the goal details.
Move Between Waiting And Active Work
Moving a board goal to the backlog preserves its article, reference, activity, status, assignee, and tag. The board becomes easier to scan, while the goal remains ready to return.
Editors can use the Move to Backlog or Move to Board action for a simple transfer. Dragging gives more control when ordering is available:
Accepted placement is preserved as more backlog results load and after the workspace refreshes. If a move cannot be saved, the goal returns to its earlier board or backlog position instead of being left in both places or disappearing from view.
Use Search And Filters Safely
Assignee and color-tag filters apply across the board and backlog together. They are useful when the full plan is large and you want to focus on one person, role, priority, or unassigned group. Search also narrows the current Goals area while respecting the viewer's access.
Changing an assignee or tag can make a row disappear immediately when it no longer matches the active filters. The goal still exists; it has simply left the filtered result.
Ordering pauses while search or filters show only part of the plan. Reordering a partial list could place hidden goals incorrectly, so clear the search and filters before dragging, inserting at a precise divider, or reorganizing the canonical backlog order.
Who Can See And Change Backlog Goals
Signed-in members can browse goals in spaces and areas they are allowed to access. Private activity membership continues to apply to backlog rows, goal details, search, and counts.
Editing authority follows the goal, not the fact that it is in the backlog:
An archived activity remains available for reviewing its existing goals, but it does not accept new backlog goals.
Common Questions
Does moving a goal to the backlog remove it from its article or discussions?
No. Only its planning placement changes. Its article, reference, activity context, and existing participation remain attached.
Is a backlog goal a draft?
No. Goals created from the current backlog composer are published immediately. The backlog describes where the goal waits in planning, not its publishing state.
Does the prepared status mean the goal is already active?
No. It records the column the goal is prepared to use when it returns. The goal stays out of that column until someone moves it back to the board.
Why can I edit a goal but not change its assignee or tag?
An assignee can work on and move the assigned goal without receiving wider coordination controls. Assignee, tag, and activity changes remain with the reporter, space owner, or a goal manager.
Why did a goal disappear after I changed it?
Check the active assignee, color-tag, and search filters. A changed goal leaves the visible results when it no longer matches them.
Why can I not drag or create between rows?
Ordering and precise insertion are unavailable while search or filters expose only part of the backlog. Dragging also depends on edit access, and creation depends on goal-management and coordinator access.