I would like it to work in a similar fashion to the process of running a series of batch files. When I queue up a series of batch files, they launch one after the other but not concurrently. I believe the "Run Tasks in order" check box makes this possible. However in the case where the task is to launch a job, this does not work. All the jobs launch. The control should not come back to the "Master" job to launch the next job, until the current job is complete.
The trigger option that you mentioned is similar to what I already do, which is to launch a job as the last task in the Queue. This works just fine, but does require me to create duplicate jobs for each needed job (one for inlcusion in a string of nightly build jobs, and one that runs as a single build).
With the solution suggested above, I would just have single build jobs for each project, then I would create a Nightly Build job that would allow me to add and remove any of the single build jobs as needed.