-
Suggestion
-
Resolution: Unresolved
-
-
Jira Software, Jira Service Management
- AUTO-1727Ability to trigger PowerShell script from Automation for Jira
- AUTO-1666Allow smart value with random function in Delay action automation
- AUTO-1726Improved management of the contextual recurring work automation rules
- AUTO-127Automation for Jira, remove the role user limit in conditions and the "to" address of the Send Email action (currently limited to roles with 50 users)
- AUTO-51Official REST API to manage rules, export/import and access automation audit logs
- AUTO-1269Log meaningful information in Audit Log when Automation Rules get Rate Limited in the backend
- AUTO-28Make it easier to navigate Automation Audit Log - add option to search/filter by Issue key, option to view more issues, option to scroll for large audit logs, link directly to the specific component rather than the overall rule
- AUTO-1370Improve sort / search / filter options on Automation Rule List
- AUTO-44Make it easier to work within Automation Service Limits, e.g. increase Daily processing time and Hourly processing time, option to reset/increase limits, show how many components a rule has, option to manage notifications of % service limit reached
- AUTO-466More ways to use code in Automation, e.g. ability to use JSON path expressions to query JSON data in web request responses
- AUTO-115Rich text editor for text fields in Automation, e.g. ability to add/update content on Confluence page
- AUTO-635 Option to configure whether the "Action" tab displays on Issue view (contains Workflow Actions and manually triggered Automation rules)
- AUTO-76Add support for custom email domains to Send Email action, to support customising the "from" and "reply-to" addresses
- AUTO-1719Provide the ability to hide/remove the "Clone when issue is done" toggle
- AUTO-138Add JSON Parser feature in Automation
- AUTO-117Make it easier to manage Automation rules with multi-project scope, e.g. by adding a new scope based on "Project Category" or "Project Type", allowing non-site admins to manage global rules if their project is in scope
- AUTO-850DevOps Automation: Actions to prioritise or rank issues to the top of backlog, retrieve top issue from backlog
- AUTO-148Improve "Clone issue" action - option to include cloning related issues, clone add-on data, make cloning errors clearer
- AUTO-525Support for Teams field in Automation, e.g. Company-Managed Projects
- AUTO-1668To-do lists (checkboxes) / action items / checklists in text fields via automation
- AUTO-1688Change the word "Add" to "Copy" when copying a single version picker field type
- AUTO-1086Improve error message when transition issue fail due to incorrect value sent using Smart Values
- AUTO-1162Allow automation rules to automatically retry actions that fail, error or timeout
- AUTO-602Option to suppress in-product / in-app notifications caused by Automation for Jira actions
- AUTO-454Support for attachments in Automation - allow file uploads / attachments using Jira API so this can be used in automation for Jira webhook
- AUTO-131The Select List (cascading) field type is currently not supported in Automation for Jira for multiple operations
- AUTO-1683Add support to Goals field in Jira Automation
- AUTO-1723Add support to Atlassian home features in Jira automation
- AUTO-1722Notification for failed rule links to global automation URL
- AUTO-1721Allow the "Branch rule / for each page owned by a deactivated account" to run for all spaces
- AUTO-744Improve "Manual trigger from issue" to support more ways to capture user input - custom issue fields, user picker field type, ability to access fields via smart values, multi-select fields, date/time fields
- AUTO-335Improve "Delete issue links" action - ability to delete a specific issue link, support for smart values
- AUTO-1562Add a built-in option to Archive Issue using Automation for Jira
- AUTO-1623Link Alerts to Issues using automation
- AUTO-1718 Support for specifying user name or ID in "Send email" action
- AUTO-1716Make it possible to send messages to shared or private MSTeams channels through Send Microsoft Teams message action component
- AUTO-63Improve Automation Template Library - allow users to add rules into the library, make playground rules exportable, make it more discoverable
- AUTO-519Add Automation support for the emailAddress value of a People field in team-managed projects
- AUTO-1007More flexible/Separate billing options for Automation limits, e.g. ability to purchase automation runs as an add-on, ability to pool limits across products, minimum allowance for Premium customers with <5 users
- AUTO-1691Ability to capture Author's name in the Jira Audit log via Jira automation.
- AUTO-1684Implement the "Issue Archived" and "Issue restored" trigger
- AUTO-1680Auto-suggest values for Boolean Smart Values
- AUTO-1677Implement safe Issue transition retry
- AUTO-1641Support Confluence folder in Jira Cloud automation rule
- AUTO-1062Ability to access other headers from an email using Smart Values
- AUTO-564Linking & syncing - automated sync of updates from linked issue, e.g. when issue is cloned
- AUTO-443Improve Microsoft Teams action - Tagging User in comments generates MS Teams message in user's individual chat, support smart values, support private channels
- AUTO-549New trigger for "Issue moved to project" and new action for "Move issue between projects"
- AUTO-1702Enhance Jira Automation to allow users without Global Jira Administrator permissions to access and set values for Tempo fields, improving usability for Project Administrators and other non-global users.
- AUTO-539Ability to export Automation Audit logs and/or access via API
1 of 490
Ability to trigger PowerShell script from Automation for Jira
-
Unassigned
-
Jun Itokawa
- Votes:
-
0 Vote for this issue
- Watchers:
-
1 Start watching this issue
- Created:
- Updated: