Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

Versions Compared

Old Version 7

changes.mady.by.user Decadis AG

Saved on

compared with

New Version Current

changes.mady.by.user Iheb Kharab

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


UI Text Box
sizemedium
typeinfo

Image AddedTriggers 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 (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 available:

UI Children


Each rule in Automation Toolbox is based on one of the following trigger types.
UI Text Box
typenote

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.

The following triggers are provided by Automation Toolbox:


Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue


Manual Trigger

Page properties
hiddentrue


Tech review

Status
colourGreen
titledone

Style guide

Status
colourGreen
titledone

Status
titletodo
Status
colourYellow
titleReady for review
Status
colourGreen
titledone
Status
colourRed
titleflagged

UI Tabs
UI Tab
titleField Changed Event
UI Tabs
UI Tab
titleScreenshot
UI Tab
titleConfiguration
UI Tab
titleUsage examples
UI Tab
titleIssue Event
UI Tab
titleIssue Transitioned Event
UI Tab
titleProject Event
UI Tab
titleScheduled Rule
UI Tab
titleSystem Event
UI Tab
title