• Rule based events run because of an action made by a user. The following are some of the ways you can use rule-based change triggers:

◦ When an item changes to a specified state, iterate over the change packages and then resync them into the reference tree.

◦ When an item is updated, change a field in a related item.

◦ If an item is in an open state and all of the reverse related items (items pointing to it) are in a final state, move the item into a final state as well.

• Scheduled events run in isolation and do not require an action by a user. The following are some of the ways you can use scheduled triggers:

◦ If the item is in a state and unchanged for a specified length of time, send e-mails to assigned users and relevant managers.

◦ If the priority is at the maximum level, send an e-mail to the manager.

◦ If a critical item has been in a beginning state for a number of days, send an e-mail to the project manager.

• Other events run when:

◦ time entry is changed by a user, for example, when a time entry is changed on an item, update the payroll system

◦ item tree is copied

◦ item is branched

◦ item is labeled

◦ test result is created, modified, or deleted