-
Suggestion
-
Resolution: Fixed
-
1,861
-
Eventually, automation rules might create a "race condition" with other features, such as connect plugins.
Having the ability to delay automation would be useful for preventing such scenarios.
Current workaround
For most situations using re-fetch issue action can be enough, but stacking them can also be done for longer updates before moving on with the rule.
- is duplicated by
-
AUTO-54 Ability to delay Automation for Jira rule executions
- Closed
-
AUTO-712 Create a "Pause" component for Automation for Jira
- Closed
- mentioned in
-
Page Failed to load
-
Page Loading...
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Form Name |
---|
[AUTO-238] Support for delay / pause / wait step in automation rule executions
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 892716 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 974161 ] |
Remote Link | Original: This issue links to "Page (Confluence)" [ 971945 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 971945 ] |
Labels | Original: jsm-s4 jsw-s13 orchestration | New: jsm-s4 jsw-s13 orchestration ribs-short |
Remote Link | New: This issue links to "Page (Confluence)" [ 948113 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 947340 ] |
Component/s | New: Rule - Edit Components [ 70298 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 944731 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 938973 ] |