What actions can an action-based dependency rule do?

In an action-based rule, you configure an entry condition and one or more actions to be taken based on the entry condition. Each action can either set an attribute's value or make it required for a user to supply a value for an attribute.

An action-based dependency rule has the following basic structure:

 If attribute A=value B and/or user role=value C, then do X, Y and Z

The entry condition (the "if" part of the rule) consists of one user role and one attribute, maximum. Examples:

If Priority=High and User Role=Developer
If Target Release=3.5
If User Role=Project Owner

The action part of the rule can either:

Set a value based on an entry condition.
Make an attribute required.

Actions that set a value

An action-based dependency rule changes the value of a target attribute based on the value of the entry condition attribute. For example, suppose that you create the following rule for the Defect artifact type:

 If Status=Code Change, then Resolution=Fixed

This rule indicates that if a user changes the status of a defect to Code Change, the Resolution field automatically is set to the value Fixed.

Actions that make an attribute required

You can define a rule that requires a user to set the value for a target attribute, that is, if a user sets a value in A, he or she is required to set the value of B. For example, suppose that you create the following rule:

 If Priority=P1, then Assignee=Required and Version To Fix In=Required

If the user sets the defect priority to P1, this rule requires the user to provide a value for the Version To Fix In field. As another example, if the user is a developer and sets the priority to High, the following rule requires the user to provide comments:

If Priority=High and User Role=Developer, then Comments=Required