This documentation applies to the 8.1 version of Change Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Test milestone - Testing the release

After a release request is approved at the Test Approval phase, you should test it at the Test milestone, before you can release it. Testers can be business staff, users, or other IT staff. They verify the release; then you can roll it out.

Release request at the Test milestone

Click the following thumbnail to expand it.


For release coordinators, the Test milestone is mostly a manual stage to verify that the service work is successful in a controlled environment. You should use the Release form to update information, revise your plans, add additional change requests and activities, and so on. At most companies, the Test milestone is interchangeable with the Build milestone.

To test the release

  1. Open the release request at the Test In Progress status.
  2. Revise the start and end dates as needed.
  3. Add changes or activities to the release as needed.
  4. Click Rollup to accumulate the risk level, costs, and time spent from the related change requests (displayed on the Manifest tab).
  5. Save your changes.
  6. Use the Process Status Flow area to move the release request from the Test In Progress status to the Deployment Approval phase.  The release must be approved before it can move forward. For more information, see Deployment milestone - Rolling out the release to the business.
Was this page helpful? Yes No Submitting... Thank you