Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-216

Improve "Send email" action - add support for e-mail templates, emailing over 90 users, send to specific user using smart value, send to all users in an organisation, default to/from addresses, email to a specific user

    XMLWordPrintable

Details

    • 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.

    Description

      Improvements

      • Add default Reply To/From addresses
      • Support for email templates These should probably be re-usable across projects and support things like header/footer/body.
      • Also provide the ability to have email messages based on locale.
      • Send Email action will only send to the first 90 users in a group (if group is greater than 90) - The Send Email action will only send to the first 90 users in a group with size > 90. This limitation is currently coming from the downstream Identity API which imposes a 90 user limit. We should send to all users in the group.
      • Add organisations field as option in the "to" field for send email action
      • Add an option on the email action to respect the JSD option for users to not be notified - If the "Reporter" clicked "do not notify" in the client portal they shouldn't be emailed
      • Improve documentation on the email action (esp recipients fields) - There are some nuances in what we show in this list and its not actually obvious what the options represent (e.g. which ones are fields, which ones are built-in values, which ones are us trying to be helpful). Would be good to add some more documentation around this
      • Ability to pick rule owner for the email action recipient field - So you don't have to type in their email address and can copy rules more easily.
      • Allow for email action to have the content to be translatable -
        This is what JSD has https://confluence.atlassian.com/servicedeskserver0311/managing-service-desk-notifications-946628493.html
      • Allow send to a specific user - So you can search for a specific person in the drop down
      • Improve automation notification emails: A4J e-mail to look like JIRA's e-mail - This could be good to have for default notifications and also for the "Send e-mail" action mail messages.
      • use 'Email from' setting from General settings in Jira
      • Ability to exclude the initiator in 'Send e-mail' action - The send e-mail action makes it possible to send to groups etc and it would be good to exclude the Initiator of the event from this. SD notifications do this.
      • Use same threading as JIRA for outgoing emails - Automation emails going to spam (make A4J e-mail look like JIRA's e-mail)
      • Improve documentation on the email action (esp recipients fields) - There are some nuances in what we show in this list and its not actually obvious what the options represent (e.g. which ones are fields, which ones are built-in values, which ones are us trying to be helpful). Would be good to add some more documentation around this
      • Send email action to a "Project lead"
      • Add a configuration option to fail a rule if email delivery fails or is unknown - Add a configuration option, likely needs to be added to the email action(s), to fail a rule if email delivery fails or if it is unknown. Unknown means SES fails to respond to our send request or reports an unknown delivery status itself after a timeout. https://jira.atlassian.com/browse/JRACLOUD-76964
      • Team managed custom fields are not pickable in Send email action

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              89403358cf11 Charlie Gavey
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: