I've witnessed huge delays between hitting a "manual build" button and seeing the plan actually be listed in the build queue. The time can range from nothing to hours, and it seems to primarily be caused by slow svn checkouts of large projects. If a bunch of large projects are sitting in an svn queue (I'm assuming there is one), the manual build seems to effectively disappear until the large projects have been built. In addition, there's no way to prioritize the manually built project in front of the large continuous integration projects - even if the CI projects are in a separate build queue, they're all waiting on SVN, so they're effectively in a single queue. To reproduce this, create some build plans with large sets of source files (we have about 14k source files in our legacy projects), make them run in a continuous integration manner, then try to run some other projects using a manual build. There's no feedback as to what is happening, and no way to get around it, which is frustrating our developers to no end. I'd be happy with either of these fixes: 1. Display projects that are scheduled for SVN polling in the build queue. That way we'd know what's really waiting for an SVN checkout - but we'd also need projects in a separate build queue to not have wait for the SVN poll for a build in another queue to complete. 2. Display a SVN queue, showing which projects are waiting for an update Either way, manually built projects should jump to the front of the SVN queue.