It's a good idea to, at the very least, decide which issues in your issue tracking system should be addressed for a particular release; this ensures that someone has considered every issue and decided whether or not it should be resolved as part of this release. This is an inherently manual process, since someone (or a group of people) has to actually examine each issue, but BuildMaster can help you make sure it gets done when it is supposed to.

Setting up Issue Tracking Integration

Of course, for BuildMaster to know the status of your issues, you must first configure Issue Tracking integration.

Add Promotion Requirements to Desired Target Environments

Next, you will need to decide which Environments you would like to block promotion to. Start by clicking the Workflows link on the BuildMaster Application sidebar. Click on an environment on the Environment Sequence diagram; I'll select the Release environment for this example.

Next, in the Promotion Requirements section, click on Add New Promotion Requirement.

Now select the Issue Tracker Status Promotion Requirement.

Now, just specify the required issue statuses to allow promotion. I will require that each issue is either marked as Resolved or Closed. The issue statuses used will depend on which Issue Tracker you are using and how you have it configured.

Now just click the Save button and your promotion requirement will be added to the application's workflow. In this example, promotion to the final environment is blocked until all issues have been resolved or otherwise closed, but you can use this promotion requirement in any environment with any issue statuses supported by your issue tracker.