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

Atlassian Automation does not respect Jira's Outgoing Email Global configuration / use the same mail sending

XMLWordPrintable

    • 0

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

      Automation for Jira sends out emails from its automation rule even if Jira's Global Configuration is configured to disable Outgoing emails from the instance. 

      Steps to Reproduce

      1. Disable the Outgoing email on an instance
      2. Configure an Automation for Jira rule to send out an email on any trigger.

      Expected Results:

      Automation for Jira does not send the email from the automation rule when the rule is executed, respecting Jira's Global configuration for Outgoing emails.

      Actual Results

      Automation for Jira sends out the email to the recipient ignoring the global configuration set by Jira's Global configuration for outgoing emails.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            [AUTO-112] Atlassian Automation does not respect Jira's Outgoing Email Global configuration / use the same mail sending

            AJohnston added a comment -

            There should at least be a banner or something that shows what is and isn't respected by the rule.

            What I'd love to see is an option to dis/allow automations to respect when outgoing mail is disabled. A child toggle, basically.

            AJohnston added a comment - There should at least be a banner or something that shows what is and isn't respected by the rule. What I'd love to see is an option to dis/allow automations to respect when outgoing mail is disabled. A child toggle, basically.

            Brett Evans added a comment -

            Definatly a bug +1,
            at very least should be clearly documented as current behavour on the outgoing mail configuration screen.

            When it says "Outgoing Mail: DISABLED" my expectations are set that ALL outgoing mail is disabled.
            If it is not then it should clearly state the caveats to that alongside this setting.

            This has potential to cause serious reputational harm to your users, especially during migrations.

            Loss of trust in your product as what other undocumented "Features" will we roll into next because its not been treated as a bug and solved or as a feature and documented clearly on the admin screen.

            Brett Evans added a comment - Definatly a bug +1, at very least should be clearly documented as current behavour on the outgoing mail configuration screen. When it says "Outgoing Mail: DISABLED" my expectations are set that ALL outgoing mail is disabled. If it is not then it should clearly state the caveats to that alongside this setting. This has potential to cause serious reputational harm to your users, especially during migrations. Loss of trust in your product as what other undocumented "Features" will we roll into next because its not been treated as a bug and solved or as a feature and documented clearly on the admin screen.
            SET Analytics Bot made changes -
            UIS Original: 3 New: 0

            Michael Scholz added a comment -

            +1 for bug. It is not neccessary for sending out E-Mails from a sandbox instance when outgoing E-Mails are disabled.

            Michael Scholz added a comment - +1 for bug. It is not neccessary for sending out E-Mails from a sandbox instance when outgoing E-Mails are disabled.

            Blake added a comment -

            Users receiving emails from automation rules running in an environment with global email disabled creates confusion. I agree, this is a bug.

            Blake added a comment - Users receiving emails from automation rules running in an environment with global email disabled creates confusion. I agree, this is a bug.
            Charlie Gavey made changes -
            Summary Original: Automation for Jira does not respect Jira's Outgoing Email Global configuration / use the same mail sending New: Atlassian Automation does not respect Jira's Outgoing Email Global configuration / use the same mail sending

            Lydia Mauti added a comment -

            This is a bug. 

            Lydia Mauti added a comment - This is a bug. 

            Otilia Ciuhat added a comment - - edited

            I see this is a "Suggestion". Can you please revisit this as it is clearly a Bug.  If I disable emailing on an instance, I expect no emails to be sent out.

            If emails still go out  ==> it is clearly a Bug.

            It's maybe a known bug, but it's still a bug; especially since there is absolutely no hint of this limitation in the interface.

            —

            Impact is huge, especially for migrations.

            Imagine you are preparing / testing a migration and  have hundreds of automations that you need to test. Some (many of them) trigger emails as well. You are confident that no emails will be sent out (since emailing is disabled); and you are anyway on a Sandbox instance. You have assured the customer as well that no emails go out

            You start testing and emails do go out. Now imagine the avalanche of confused end-users and the, at best, disappointed customer.

             

            Otilia Ciuhat added a comment - - edited I see this is a "Suggestion". Can you please revisit this as it is clearly a Bug.  If I disable emailing on an instance, I expect no emails to be sent out. If emails still go out  ==> it is clearly a Bug. It's maybe a known bug, but it's still a bug; especially since there is absolutely no hint of this limitation in the interface. — Impact is huge, especially for migrations. Imagine you are preparing / testing a migration and  have hundreds of automations that you need to test. Some (many of them) trigger emails as well. You are confident that no emails will be sent out (since emailing is disabled); and you are anyway on a Sandbox instance. You have assured the customer as well that no emails go out You start testing and emails do go out. Now imagine the avalanche of confused end-users and the, at best, disappointed customer.  

            Tim Eddelbüttel added a comment -

            Seriously?

            Tim Eddelbüttel added a comment - Seriously?

            Julian Vornehm added a comment -

            +1

            We're having this issue with a sandbox environment used for our Server to Cloud migration. Users are getting confused by notifications about old tickets since the sandbox is not up to date with the Jira Server.

            Julian Vornehm added a comment - +1 We're having this issue with a sandbox environment used for our Server to Cloud migration. Users are getting confused by notifications about old tickets since the sandbox is not up to date with the Jira Server.

              eeb2e5a08fc6 Srini Chakravarthy
              f8dac69712b5 Eshan Anchan
              Votes:
              101 Vote for this issue
              Watchers:
              65 Start watching this issue

                Created:
                Updated: