Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    JIRAAUTOSERVER-1129Allow Automation triggers to detect issue creation as a transition
  2. Suggestion
    JIRAAUTOSERVER-749Implement the "Advanced branching" functionality
  3. Suggestion
    JIRAAUTOSERVER-313Support access of all Insight attributes through smart values
  4. Suggestion
    JIRAAUTOSERVER-832Automation rule should provide correct error message when rule scope has an archived project
  5. Suggestion
    JIRAAUTOSERVER-382Changelog to trigger the last issue changes without needing to specify the custom fields with smart values
  6. Suggestion
    JIRAAUTOSERVER-254Allow user who triggered event to be rule Actor
  7. Suggestion
    JIRAAUTOSERVER-1098Add the option to disable the "Create rule templates" button
  8. Suggestion
    JIRAAUTOSERVER-1121On an Epic, Display Points Metrics of Child records - Total, Done, Say/Do
  9. Suggestion
    JIRAAUTOSERVER-1128Implement Switch/Case logic in Jira Automation for Data Center
  10. Suggestion
    JIRAAUTOSERVER-836Allow Jira Project Administrator role to import/export Automation rules
  11. Suggestion
    JIRAAUTOSERVER-1093Support for Advanced Roadmap fields in Automation for Jira
  12. Suggestion
    JIRAAUTOSERVER-159Provide Support for Portfolio/Advanced Roadmaps for Jira fields (Team, Target Start, Target End)
  13. Suggestion
    JIRAAUTOSERVER-741Add the ability to clone sub-tasks and linked issues when cloning a Jira issue
  14. Suggestion
    JIRAAUTOSERVER-877Lookup issue action - Add support for more fields
  15. Suggestion
    JIRAAUTOSERVER-407Allow to change default values in automation before ticket creation
  16. Suggestion
    JIRAAUTOSERVER-163A trigger for when a watcher is added/removed/updated to an issue
  17. Suggestion
    JIRAAUTOSERVER-1124Include a small snippet of the summary in the automation rule
  18. Suggestion
    JIRAAUTOSERVER-1123Improve Automation audit log - include more info, option to include additional detail in audit logs / issue history, keep history for more than 90 days
  19. Suggestion
    JIRAAUTOSERVER-51Add {{approval.buttons}} smart value to add service desk approval buttons to emails sent via automation rule
  20. Suggestion
    JIRAAUTOSERVER-16"On Clone" as Automation trigger
  21. Suggestion
    JIRAAUTOSERVER-1016Add actual ability to create/delete/manage "Template Rules"
  22. Suggestion
    JIRAAUTOSERVER-1120As a Jira admin, I want to allow users to A4J rule impersonation permissions to be able to select from a specific list of "pre-approved" users as the rule actor
  23. Suggestion
    JIRAAUTOSERVER-287Field value changed trigger should support insight fields
  24. Suggestion
    JIRAAUTOSERVER-1028Improve "Send email" action - add support for e-mail templates, emailing over 50 users, send to specific user using smart value, send to all users in an organisation, default to/from addresses, email to a specific user
  25. Suggestion
    JIRAAUTOSERVER-988Forms submitted trigger
  26. Suggestion
    JIRAAUTOSERVER-1116Provide the option to use ISO 8601 DateTime format for Assets compatibility
  27. Suggestion
    JIRAAUTOSERVER-281Reload/Refresh the Jira issue when an automation rule makes updates to it
  28. Suggestion
    JIRAAUTOSERVER-261Ability to copy components when creating/updating a rule
  29. Suggestion
    JIRAAUTOSERVER-1051Have an option to select the "secret key" as the URL for "Send Web request" action
  30. Suggestion
    JIRAAUTOSERVER-991Add the feature "Prompt for input when this rule is triggered" under manual trigger in Jira DC
  31. Suggestion
    JIRAAUTOSERVER-338Ability to send a ticket attachment using Send Mail function
  32. Suggestion
    JIRAAUTOSERVER-464Update Insight Object attribute value using JSM/Jira automation on Data Center
  33. Suggestion
    JIRAAUTOSERVER-135Support "Parent Link" fields
  34. Suggestion
    JIRAAUTOSERVER-229Official REST API to manage rules
  35. Suggestion
    JIRAAUTOSERVER-1063Monitor Automation events queue health
  36. Suggestion
    JIRAAUTOSERVER-372Add the ability to automatically approve or decline requests using a rule from Automation for Jira
  37. Suggestion
    JIRAAUTOSERVER-273Ability to override outgoing webhook timeout value from the UI
  38. Suggestion
    JIRAAUTOSERVER-125Add support for 'Cascading select' fields in the simple form
  39. Suggestion
    JIRAAUTOSERVER-203Allow Rule Actor to be dynamically set
  40. Suggestion
    JIRAAUTOSERVER-186Support holidays in date manipulation functions
  41. Suggestion
    JIRAAUTOSERVER-581Implement an Automation Rule Action to show a message in the form of an AUI Flag to the user
  42. Suggestion
    JIRAAUTOSERVER-1067Smart values to access to A4J secrets
  43. Suggestion
    JIRAAUTOSERVER-1089Send notifications through different channels when automation rules fail
  44. Suggestion
    JIRAAUTOSERVER-1110Automation for Jira - Add a trigger for Group Membership changed
  45. Suggestion
    JIRAAUTOSERVER-1109Expand the A4J automation search functionality
  46. Suggestion
    JIRAAUTOSERVER-352Notify user on failure
  47. Suggestion
    JIRAAUTOSERVER-1108Add a workflow post function to trigger a rule
  48. Suggestion
    JIRAAUTOSERVER-131Smart value to get last added (in time) attachment
  49. Suggestion
    JIRAAUTOSERVER-512Make it easier to manage Automation notifications - who receives them, enabling/disabling notifications, new notifications for rule changes
  50. Suggestion
    JIRAAUTOSERVER-1105Add to the Audit Log the result of condition matching
Refresh results
1 2 3 4 5Next >>
1 of 541
Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-1129

Allow Automation triggers to detect issue creation as a transition

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Triggers
      • ril
    • 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.

      Currently in Automation for Jira, an issue is either created or transitioning between states in a workflow. These do not overlap. This can cause issues where an Automation is looking for a transition to a status from any status but the initial status is null ( new issue ) so it never fires.

      For ease of using Automation for Jira, it would be beneficial to add an option to detect issue creation as an issue transition for this trigger or allow the Automation for Jira to detect the transition from create to a status.

        links to

        Web Link Internal ticket

              • All
              • Comments
              • Work Log
              • History
              • Activity

                Unassigned Unassigned
                d063a923034e John Vecchio
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Created:
                  Yesterday 6:47 PM
                  Updated:
                  Yesterday 10:31 PM
                  • Atlassian Jira Project Management Software
                  • About Jira
                  • Report a problem
                  • Privacy policy
                  • Notice at Collection

                  Atlassian