Enforce a workflow

Project Tracker allows you to set transition rules for selecting attribute options for attributes with the input type "drop down list".

These transitions can be used to define the workflow and enforce processes within the project. You can also use these transitions to determine which users are able to perform certain tasks. For example, you can set your transitions so that only users with a quality assurance role are able to resolve or close artifacts. Doing this would insure that all artifacts are reviewed by quality assurance.

You can set transition rules to be applied when the attribute is first given a value or when its value is changed. These rules can be applied to specific roles. You can also set rules to require that other attributes in the artifact have defined values.

Setting transition rules based on the users' roles allows you to define which users are able to enter or change artifacts with certain options. For example, if you want to ensure that only artifacts that have been reviewed by a project owner can be escalated to P1 in priority, you could hide the P1 option for the Priority attribute for all roles except Project owner.

Setting transition rules that require other attributes to have values before an option becomes visible allows you to ensure that any processes you have defined are followed in your project. For example, if your processes require that artifacts must be given a priority before they can be assigned to a milestone, you can set the transition rules so that the priority attribute must be defined before the options for the Milestone attribute become visible.

Once the transitions are defined, when an artifact of this artifact type is created or edited the specified transition rule gets applied. The settings are validated at the time of submitting or saving the artifact. The artifact cannot be saved if the specified attribute option transition settings are not executed.

Setting transition rules

The Project Tracker administrator can set transitions within global artifact types. When the artifact type is added to a project, the globally set transitions are applied; however, they can be overridden at the project level. The globally defined transitions are not applied to projects in which the the artifact type was added before the transitions were defined. For globally defined transitions to be applied to projects already using the artifact type, the artifact type must be removed from the project and then reapplied after the transitions are defined.

If you define transition rules in a project, any new sub-projects that are created will inherit those transition rules. The transition rules can be overridden in the sub-project without affecting the parent project.