Configuring phase and exit criteria milestones

You can enforce milestones that require the completion of all change requests and activities before the release can move to the next milestone. For example, you can configure Release Management so that all the Planning activities must be completed before the release can move to the Build stage.

The Release Milestone Configuration form allows you to define phases, as well as the exit criteria, for each milestone.

To configure phase milestones

You can use this form to localize release milestones. 

1. In the Application Administration Console, click the Custom Configuration tab.
2. From the Application Settings list, select Release Management > Advanced Options > Milestone Configuration, and then click Open.
   You can filter table results by using the Show Locale and Show Phase menus. The Show Phase menu only shows phases defined for the locale you are in.
3. In the Phase Name field, define the Deployment phase that requires a milestone (for example, Phase 1 or Phase 2).
4. Select a locale from the menu, and then click Add to create a new locale for the Deployment milestone (for example, en_AU for Australian English).
5. Define the localized text for each phase by performing the following actions:
   1. After adding a phase, select the phase from the table, and then click Manage Locales.
      The Defined Locales dialog box appears, where you can add localized text for the selected phase.
      
      
      
   2. Enter localized text into the Phase field.
   3. Select the locale.
   4. Click Add.
      You can modify or delete localized text as needed.
   5. Close the Manage Locales dialog box when you are finished.
      The localized text appears in the Release Milestone Configuration form.
   6. Close the Release Milestone Configuration form when you are finished.

Configure exit criteria

Exit Criteria defines which action should occur (for example, Warning or Error) at the exit of each milestone. 

In addition to the exit criteria supplied out of the box for you, the Release Management administrator can define new exit criteria. You can configure exit criteria for each company, or create new global priorities. If you create and enable new exit criteria, it overrides the default setting, unless you disable it. For example, the following exit criteria indicate that, before a release for Acme, Inc. can exit the Deployment milestone, the system must verify that all changes are in Completed status:

• Milestone = Deployment
• Request Type = Change
• Status to Check For = Completed
• Action = Error

If they are not, the system displays an error message.

To configure exit criteria

1. In the Application Administration Console, click the Custom Configuration tab.
2. From the Application Settings list, select Release Management > Advanced Options > Milestone Configuration, and then click Open.
3. Click the Exit Criteria tab.
4. In the Milestone field, specify the release milestone (for example, Deployment).
5. In the Request Type field, specify the application request type (for example, Activity). 
   You can specify the following types:
   • Change
   • Activity
   • Change and Activity
6. In the Status to Check For field, specify the release status (for example, Completed or Closed).
7. In the Action field, specify the level of enforcement that applies to the release criteria (for example, Warning or Error).
8. Click Add.