Page History
hidden | true |
---|
Status | ||
---|---|---|
|
Status | ||
---|---|---|
|
Status | ||
---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
On this page
|
UI Text Box | ||||
---|---|---|---|---|
| ||||
Triggers define whether when a rule should be executed - so every rule starts with a trigger. or not. 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 |
(e.g. "A field was updated", "A new version was created"). Apart from events, a trigger can be:
|
|
Available automation triggers
The following triggers are
provided by Automation Toolboxavailable:
UI Children | sort | title
---|
UI Text Box | ||
---|---|---|
| ||
A trigger must be the first element in the rule configuration and can only occur once per rule | ||
UI Text Box | ||
| ||
. For For the rule to execute, the conditions configured for a chosen trigger must be met. |
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Page properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|