Creating configurations

To configure separate preconditions or follow-up actions for different roles or time periods, you must specify multiple configurations. You can either create a new configuration or copy an existing configuration and then edit it. Typically, you create a configuration if no similar configurations exist for you to copy.

Before you begin

You must have permission to modify the project area or team area where you want to create a configuration.

About this task

Note: If multiple preconditions are specified for an operation, all of the preconditions are evaluated, even if one of them fails. This behavior ensures that users are alerted to all unsatisfied preconditions that would cause the operation to fail.

Procedure

  1. Navigate to the project area in the administrative web interface. See Logging in for project administrators and team leads (web). To set preconditions or follow-up actions for a team area, click the team area in the Team Hierarchy section.
  2. In the project area or team area, click Preconditions & Follow-up Actions. The Preconditions & Follow-up Actions page opens and shows the existing configurations for the project area or team area, as in the following example:
    The Preconditions and Follow-up Actions page in the web client. A table has the following columns: What, Who, When, Summary, and Actions. Two operations are shown: Generate Team Invitation and Save Work Item. The Who column shows the Everyone role. The When column shows Always. The Summary column for the Generate Team Invitation operation shows 1 follow-up action. The Summary column for the Save Work Item operations shows 1 precondition.
  3. Click Configure > Create New Configuration.
  4. In the Create New Configuration wizard, complete the steps as follows:
    1. Expand the operation category to select the operation for which to configure a precondition or follow-up action and click Next.
      The first page of the Create New Configuration wizard. The operation pane shows a tree hierarchy of operations. The Work Items node is expanded and the Save Work Item operation is selected.
    2. Select the role for which the precondition or follow-up action will apply and click Next.
      Note: Because all users are assigned the default Everyone role, you can have specific operation behavior apply to all users by specifying it for the Everyone role; you need not specify it for every role. At runtime, Rational Team Concert™ checks the operation behavior settings for all other roles assigned to the user before checking the operation behavior for the Everyone role. If operation behavior is specified for one of those roles, Rational Team Concert uses that operation behavior instead of the operation behavior that is specified for the Everyone role.
    3. Select whether the configuration should apply all the time, for only a specific timeline or iteration, or for only iterations of a specific iteration type, and click Finish. The wizard closes and the Preconditions & Follow-up Actions page shows the new configuration with no preconditions or follow-up actions specified, as illustrated in the following image:
      The new configuration open in the editor. The Preconditions pane shows that no preconditions are configured.
  5. Click the Add icon Add icon; then select a precondition or follow-up action.
  6. If the precondition or follow-up action provides additional configuration settings, specify those settings. For example, you can configure the Prevent Editing precondition, which is shown in the following image, to apply to specific work item types and states.
    Note: In the current release, only a subset of preconditions and follow-up actions that require additional details can be configured by using the web UI. For all other preconditions and follow-up actions, you must use the Rational Team Concert client for Eclipse IDE to configure them.
    The configuration editor. In the Preconditions pane, the Prevent Editing precondition is selected. The Description field describes the precondition. All work item types are listed. Arrows next to each type indicate that they can be expanded. The Defect work item type is expanded to show its five work item states. Each state has a check box.
  7. Optional: Add more preconditions or follow-up actions.
  8. Optional: To prevent child team areas, or project areas that consume the shared process of this project area, from customizing this configuration, select Final (ignore customization of this operation in child areas).
  9. To save the new configuration, click Save.

Results

The new configuration is created and is listed with the other configurations.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki