Using Schedule Stage
Summary: 
What is the Scheduled Stage?
The scheduled stage determines whether we activate the Start Date, End Date, Duration, and show tasks on the calendar. Otherwise we do not use the start, end, duration properties, or show it on the gantt and timeline charts.
Moving a Task into Scheduled Stage makes it appear on the Gantt Chart and Timeline.
If it has not been in scheduled stage, it will not be flagged to appear on the gantt chart and Timeline.
How Do I know what's Scheduled and Not?
Use the these controls to toggle between showing Unscheduled (Left selected), Scheduled (right selected) and Both (neither selected)
Why do we want a Scheduled Stage?
To make it easy to maintain a backlog of possible work, to schedule some of the work, yet keep the unscheduled backlog off the gantt chart.
For example, lets use the simple workflow: Ideas -> Backlog -> Scheduled -> Work -> Complete -> Closed.
In Agile terms, you would schedule your planned sprints or iterations, and leave the rest of the backlog off the schedule.
Runcible allows you to combine the backlog of agile management, with the resource scheduling of traditional Work Breakdown Structures: taking the best of both worlds.
Think of it this way: You can use (a) a traditional WBS, scope, change requests, phases, dependencies, dates, and a variable staff. Versus (b) a backlog of various phases or iterations, each hitting a scheduled date using a variable staff. Versus (c) iterations of the same size and duration using a fixed staff.
So Runcible lets you do what you want to or need to without asking you to demonstrate religious devotion to a methodology. Our methodology is 'give people information' and 'make information transparent', and people will succeed.