It’s important to designate the context to test and reproduce errors:
Testing in different environments shows application dependencies from installed components, or features of auxiliary software.
Builds can be added manually prior to start of testing. However, it’s better to integrate release system for builds (build server, e.g., Jenkins or TeamCity) and Devprom ALM. In this case, builds (their numbers and locations) will be registered automatically at the moment of their release. You can do this using REST API simple commands examples of which you can see in the context help for "Builds" module.
For each build, you can discover the implemented requirements, detected errors, and filled test reports. You can discuss the build, e.g., speak about its readiness to migrate to the next stage of quality control system.
You can also add environments manually, or using REST API. For example, if you have a dynamic test environment, i.e. you use virtual machines or docker containers, you can register environments at the moment of their creation prior to launching of automated tests.