Administer Jira automation
Jira Data Center automation
- Get started with Jira automation
- Administer Jira automation
- Create and configure Jira automation rules
- Components in Jira automation
- Smart values in Jira automation
- Use Jira automation rules to modify issues
- Monitor automation activity and diagnose issues
- Set a rule to create a Confluence page
- Jira Data Center automation release notes
On this page
In this section
- Understand versions, licenses, upgrades
- Use automation with other applications
- Checking URLs against the Jira allowlist
- Setting configuration properties
- Manage permissions for project admins
- Automation rule not working after removing the rule actor license
- Automation rule to reopen/close the Epic if a belonging Story gets reopened/closed accordingly
- Issue event in jira trigger duplicate notifications for the "Field value changed" trigger in automation rules
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications
These pages will help you work with Jira automation as a Jira admin.
- Understand versions, licenses, upgrades
- Use automation with other applications
- Checking URLs against the Jira allowlist
- Setting configuration properties
- Manage permissions for project admins
- Automation rule not working after removing the rule actor license
- Automation rule to reopen/close the Epic if a belonging Story gets reopened/closed accordingly
- Issue event in jira trigger duplicate notifications for the "Field value changed" trigger in automation rules
Last modified on Apr 6, 2022
In this section
- Understand versions, licenses, upgrades
- Use automation with other applications
- Checking URLs against the Jira allowlist
- Setting configuration properties
- Manage permissions for project admins
- Automation rule not working after removing the rule actor license
- Automation rule to reopen/close the Epic if a belonging Story gets reopened/closed accordingly
- Issue event in jira trigger duplicate notifications for the "Field value changed" trigger in automation rules
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications
Powered by Confluence and Scroll Viewport.