Builds | Targetprocess - Visual management software


A Build is an important part of the development process. Usually it represents a version of the software which consists of a set of new features and bug fixes that are going to be released to the end users.

Builds. Image 1

Built-in Links to Builds

Originally, the Build entity type was created for the testing area. It was used to track the build a defect was found in and a test plan run has been executed.

A Build can be assigned to a Release and a nested Iteration.

Built-in Links to Builds

Releases and Iterations are supported as lanes on views that display Builds as cards. Detailed views of Releases and Iterations do not have Builds tab.

A Build cannot be assigned to a Team Iteration.

If you open a details view of any Bug you will see Build field in the Info section:

bug build

Test Plan Run entity has the same field as well.

Builds. Image 4

Release and Iteration are inherited for Test Plan Runs from Builds. When you assign a Build to a Test Plan Run, an Iteration and Release of the Build are assigned to the Test Plan Run automatically. When a Test Plan Run is assigned to a Release or an Iteration, you can assign it to a Build from the Release / Iteration only.

Release and Iteration of Bugs are independent from the ones assigned to a related Build.

Builds are supported as lanes on views that display Test Plan Run as cards. Builds are incompatible with Bugs this way.

Unfortunately, Bugs and Test Plan Runs are not displayed as tabs in detailed views of Builds.

Relations to Builds

After a while, we started to use Builds in a different way. Once the new version is ready, we add a new Build under Relations to all Features and User Stories that are released in this Build as well as all Bugs that were fixed. By doing so, we can easily track which items were released in a particular Build.

Relations to Builds

New Build can be created using the main +Add button:

add build

Once the Build is created you can assign it to a Feature, User Story, Bug or another Entity using the Relations tab:

build relations

To see the detailed information of all the Builds, you can use a Board View with Outbound (or Inbound) Relations filtered by Build entity type:

build details
The Build entity does not have its own Workflow. Though, when it is necessary to track the status of Builds, Custom Fields of Drop Down type can help:

build status

System Settings

Customize Roles Permissions to remove the ability to create / edit / delete Builds. It is not possible to disable Builds as entity types in the system completely.

Still have a question?

We're here to help! Just contact our friendly support team

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.

Or contact
a sales representative

Get a live
product demo

Let one of our product specialists create your account
and shape Targetprocess for your company needs.