Page History
Page properties | |||||
---|---|---|---|---|---|
| Status | ||||
Tech review |
| ||||
Style guide |
|
Status | ||
---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
size | medium |
---|---|
type | info |
Triggers define when a rule should be executed - so every rule starts with a trigger.
A trigger must be the first element when configuring a rule , and can only occur once per rule. Triggers will generally listen to events. Typical events are field, issue, project, or system events , but can also be (e.g. "A field was updated", "A new version was created").
Apart from events, a trigger can be:
- scheduled to only be executed at certain times
Apart from the scheduled and manual triggers all triggers are based on events.
Part of the graphic used on the overview page?
|
Available automation triggers
The following triggers are available:
ui-children | ||
---|---|---|
|
UI Text Box | ||
---|---|---|
| ||
A trigger must be the first element in the rule configuration and can only occur once per rule. For the rule to execute, the conditions configured for a chosen trigger must be met. |
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Page properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|