Revision as of 01:10, 21 April 2009

ATS - Action Tracking System

The Action Tracking System (ATS) is a tightly integrated change tracking system that manages changes throughout a product's lifecycle. ATS provides integrated change management to all OSEE applications through user customizable workflows.

Configuring ATS

Configuring ATS for Multi-Branch committing...

Branch Configuration Attributes:
ats.Allow Branch Create - activates ability to create working branches from parent
ats.Allow Branch Commit - activates ability to commit working branches to parent
ats.Parent Branch Id - set to the branch id of the branch to create/commit

If ATS - Team Definition attribute "ats.Team Using Versions" == false, then ATS uses branch configuration attributes from Team Definition.

Else If ATS - Team Definition attribute "ats.Team Using Versions" == true, then ATS uses branch configuration attributes from targeted ATS - Version Artifact. This means that the ATS - Team Workflow must be targeted to a version before branching can occur

Configuring ATS for Change Tracking

The Action Tracking System (ATS) can be configured for tracking changes made to such things as requirements, software, hardware and facilities.

The integrated nature of ATS also allows for the tight configuration management of changes to the artifacts that are stored and managed in OSEE, such as requirements, and provides advanced features that allow for advanced workflow management of these items.

OSEE ATS provides a few levels of configuration, from the simple/dynamic configuration that can be created/modified during runtime to a more advanced configuration that requires a separate plugin and release/update.</p>

1. Create a New configuration using the ATS Configuration Wizard
1. Select File -> New -> Other -> OSEE ATS -> ATS Configuration
2. Enter in a unique namespace for your configuration (eg: org.company.code)
3. Enter in a name for the Team that will be performing the work (eg: Code Team)
4. Enter in a list of Actionable Items that you want the users to write change requests against. (eg: Editor, Installer, Website)
5. If Actions are to be grouped and released in versions (or builds), enter a list of versions. (eg: 1.0.0, 1.1.0, 1.2.0) Otherwise, this field may be left blank.
6. If an existing workflow (eg: osee.ats.teamWorkflow) is to be used, enter this as the id. Otherwise a new workflow will be created.
7. Upon Selecting Finish, ATS will be configured with the entered information. You can then select to create a new Action and select one of the Actionable Items (named above). This will create a new workflow and assign it to the above Team for processing.
8. See <a href="../ats/ATS.htm#section8.1">Configure ATS for Change Tracking</a> for more information.
2. Creating a New workflow configuration for existing Team / Actionable Items using the ATS Workflow Configuration Editor
1. Select File -> New -> Other -> OSEE ATS -> ATS Workflow Configuration
2. Enter in a unique namespace for your configuration (eg: org.company.code)
3. Upon Selecting Finish, ATS will create a simple workflow that can be expanded with new states, transitions and widgets.
4. This workflow will need to be related to the Team Definition that will use it. See <a href="../ats/ATS.htm#section8.1">Configure ATS for Change Tracking</a> for more information.
3. Editing an existing workflow configuration using the ATS Workflow Configuration Editor
1. In the Branch Manager, set the Default Working Branch to the Common branh.
2. In the Artifact Explorer, expand Action Tracking System -> Work Flows and select the workflow to edit. This will open the ATS Workflow Configuration Editor.
3. Workflow can be edited to include new states and transitions. Double-click state to relate widgets and rules.
4. Selecting Save will validate the workflow and save the changes to the database. These changes can be used immediately by Team Definitions configured to use this workflow.
5. See <a href="../ats/ATS.htm#section8.1">Configure ATS for Change Tracking</a> for more information.
4. Advanced ATS Configuration via the org.eclipse.osee.ats.config.demo - Although ATS can be configured dynamically in a runtime environment, advanced configuration, like creating new widgets and rules, can be done through extension points. The ats.config.demo plugin is an example of these capabilities.