User interface

1. Adds concept of user groups to manage large amount of users.
2. Allows anonymous access and define permissions for anonymous users.
3. Tree organized build configurations make navigation through large number of projects easy.
4. Utilizes concept of inheritance and overriding to reduce complexity of configuring and managing large number of projects.
5. Build can be promoted from one state to another, for example, from "test" state to "release" state. Version can be changed in similar fashion, for example, from "myproduct.QA.5" to "myproduct-1.1".
6. Easily build against specified label, or branch by using variables.
7. Ability to define build queues to control concurrent number of builds.
8. OGNL expression helpers.
9. A dashboard page used to perform all routine jobs.
10. Intuitive error reports for invalid data inputs.

Version Control System support

1. Ability to specify comments while creating a label in a version control system repository during the build process.
2. Ability to use revision number of Subversion version control system to construct build version.

Builder support

1. Artifacts published to Maven repository are accessible from QuickBuild's web interface.
2. Supports builds for .NET projects through NANT.

Build promotion

1. Be able to promote build from one configuration into another (for example, from QA to Release). The new build can take next build version of the destination configuration, or just use the original build version. Combined with the build permission management and build notification, builds can flow smoothly between different roles of your team.
2. Source code of original build can be re-labeled as part of the build promotion process.
3. Promoted build can use artifacts of original build directly, or can be re-produced using exactly the same set of source code of the original build.
4. Build can be promoted between different machines.
5. With the build promotion feature, one can select a particular build and run additional steps to further process it (for example, deploy it into the integration test machine).

Build notification

1. Build notifications can be sent to developers who checked in since the last successful build.
2. Build log or revision log can be attached to Email.
3. Error lines in build log can be extracted and inserted into Email directly.
4. Users can self-manage their subscriptions to certain build events.
5. RSS for build search results, so that user can be notified of new builds satisfying the search criterion.

Build process

1. Remote and parallel build support:
   1. Set up build for projects which consist of components that should be built on different OS platforms.
   2. Ability to build different parts of a project on different build machines simultaneously, to speed up build process.
   3. Ability to build projects at one machine, and publish the generated build results to another machine for automation/smoke tests. Testing report can be collected and published back to the main build machine for later review.
2. Fully customizable build process, you can define your own build steps.
3. Ability to control what steps should be executed serially, and what steps can be executed simultaneously (to speed up the build process).