Open issues

Order by Priority
  1. Suggestion
    AUTO-1915Ability to manually set the username on the workday trigger
  2. Suggestion
    AUTO-1769Ability to know the result of "send email" action in Automation rules
  3. Suggestion
    AUTO-374A4J: Support additional properties and functions for smart value {{lookupIssues}} e.g. ability to add / multiple values, due date, worklog property
  4. Suggestion
    AUTO-602Option to suppress in-product / in-app notifications caused by Automation for Jira actions
  5. Suggestion
    AUTO-32Rule orchestration - allow switch between parallel and sequential execution of Automation Rules, e.g. via wait/delay step
  6. Suggestion
    AUTO-1914Automation for Task Assignment Based on Daily Logged Hours
  7. Suggestion
    AUTO-1913Log individual actions processing time in Automation Rules to allow users adapt their rules for a better performance
  8. Suggestion
    AUTO-1285Having the ability to identify the automation rule using existing webhook
  9. Suggestion
    AUTO-1430Automation Action Send Web Request: Provide a Smart Value to get the RAW JSON for a web request response.
  10. Suggestion
    AUTO-1206Increase max components per rule
  11. Suggestion
    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
  12. Suggestion
    AUTO-1912Improve field searcher within the automation rule editor
  13. Suggestion
    AUTO-1699Official REST API to check the current Jira automation usage per product
  14. Suggestion
    AUTO-216Add support for email templates to "Send Email" action
  15. Suggestion
    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
  16. Suggestion
    AUTO-159Improve Automation concurrency - request for expanding resources in automation, give visibility of how many number of concurrent executions are available in Automation, support monitoring of Automation queue
  17. Suggestion
    AUTO-992Product changes may cause Automation Rules to count towards the Wrong Product Limit
  18. Suggestion
    AUTO-1728Provide the ability to specify the storage path in the 'Create Doc in Google Drive' action
  19. Suggestion
    AUTO-1694Action 'Create Slack channel for incident' should include an option to make channel private
  20. Suggestion
    AUTO-1911Create Slack channel for incident should store the Channel ID in a smartvalue
  21. Suggestion
    AUTO-1729Allow Manual input for the Project and Issue type Field In Create Issue Step
  22. Suggestion
    AUTO-1733More granular Permissions for Automation: "Edit Global Automation" in the Jira Permission, allow project admins to import rules
  23. Suggestion
    AUTO-803Unable to search "Category" field in Automation for JIRA Cloud
  24. Suggestion
    AUTO-1871Block importing duplicated incoming webhook trigger to prevent locking the rules from being editable
  25. Suggestion
    AUTO-525Support for Teams field in Automation, e.g. Company-Managed Projects
  26. Suggestion
    AUTO-1750Improve the error message for wrong referencing smart values.
  27. Suggestion
    AUTO-36Improve Automation audit log - include more info, option to include additional detail in audit logs / issue history, keep history for more than 90 days
  28. Suggestion
    AUTO-549New trigger for "Issue moved to project" and new action for "Move issue between projects"
  29. Suggestion
    AUTO-76Add support for custom email domains to Send Email action, to support customising the "from" and "reply-to" addresses
  30. Suggestion
    AUTO-1909Enable Automation Rules to Recognize Comments Added via Mail Handler
  31. Suggestion
    AUTO-51Official REST API to manage rules, export/import and access automation audit logs
  32. Suggestion
    AUTO-1633API tokens usage in the authorization header for the "Send web request" action
  33. Suggestion
    AUTO-1782Automation Rule builder to use project fields for TMP projects
  34. Suggestion
    AUTO-1562Add a built-in option to Archive Issue using Automation for Jira
  35. Suggestion
    AUTO-1907Provide a component for counting work items returned in JQL
  36. Suggestion
    AUTO-126Contextual dropdowns - limited results shown in dropdown for issue fields, allow for easier custom field selection when there are duplicates in automation rules
  37. Suggestion
    AUTO-1705Unsupported characters in smart values break JQL
  38. Suggestion
    AUTO-1906Ability to set groups/teams/multiple user as a owner in Automation rule
  39. Suggestion
    AUTO-1661Forms Submitted trigger in JSW projects
  40. Suggestion
    AUTO-289Automation: Need a new action to add web links to an issue
  41. Suggestion
    AUTO-736Improve "Create Lookup Table" action - allow lookup table keys to populate multi fields when the value is comma-separated
  42. Suggestion
    AUTO-1130Ability to include ticket attachments and image attachments using Send Mail function
  43. Suggestion
    AUTO-451A4J - Provide the ability to suppress email notifications for create issue, transition issue, assign issue and delete issue actions
  44. Suggestion
    AUTO-1905Improve the Audit log for the Manage watchers action
  45. Suggestion
    AUTO-476Automation for Jira - Add the functionality of publishing comments with restrict visibility for Project Roles
  46. Suggestion
    AUTO-1904Allow Automation Rovo Agents to provide requests for additional information
  47. Suggestion
    AUTO-1903Creation of a component to check if the trigger issue is still valid.
  48. Suggestion
    AUTO-1902Improve the error message when automation rule fails if the trigger issue is no longer valid (archived, deleted)
  49. Suggestion
    AUTO-1109Manual Trigger Automation should show results of rule execution, e.g. notification if issue is created
  50. Suggestion
    AUTO-1896Ability to use wildcards when adding restrictions to automation components.
Refresh results
1 of 546
Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-1915

Ability to manually set the username on the workday trigger

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      When configuring a rule to trigger for when a worker is added to Workday, the trigger configuration sets the username as the rule's owner.

      To change the username, you need to change the rule's owner. 

      It would be great if we could change the trigger's username without changing the rule's owner.

      An example use case is to have an admin as an owner to receive updates when the rule fails, but use a service account to receive the payload from Workday.

              Unassigned Unassigned
              877ac19b0be8 Nataniel Rocha
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: