Use of tasks

A task represents a problem in or enhancement to your software application. Because a task categorizes all of the objects you are modifying for a specific problem or enhancement, you need to complete only the task that categorizes those objects. You do not need to check in the objects individually. Tasks do much of the work for users.

By default, any Rational Synergy user (developers, build managers, and so on) can create a task. Tasks can also be generated and assigned based on change requests submitted by customers or technical support engineers.

When users create a task, they can immediately assign it, if they know who needs to resolve the problem. For example, a build manager can assign a task to himself or another user. The user who creates a task can assign it to himself. When users assign a task, they must set its release value to indicate the version of the software application in which it is included.

After tasks are assigned, developers use the following process:

  1. Select a task to be the current task.

    Select any of your assigned tasks to be the current task.

  2. Make all necessary changes to complete the task.

    Because Rational Synergy automatically associates all object versions you change with the current task, any object on which you perform an action is associated with the current task.

    Perform unit testing so you know whether additional modifications are required.

  3. Complete the current task.

    When you complete the task, Rational Synergy first checks in the objects associated with it. Then, the task is completed. Completed tasks are available to the build manager for integration testing and to the build manager for further integration and system testing. After completed tasks pass integration testing, the build manager makes them available to other developers.


Feedback