• Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • None
    • None
    • None

      Currently, as mentioned here: Manage product sandboxes, when creating a Sandbox environment and performing Copy Data to production, by default, the Global Mail Settings - Email puller on Sandbox is set to disabled. The only way to enable this is contacting support, as it is disabled by a system flag.

      It would be nice for Org Admins to have the ability to enable or disable it on Sandbox side.

       

       

          Form Name

            [CLOUD-11243] Ability to enable Global Mail Settings - Email puller on Sandbox

            +1

            This should be disabled after a sandbox copy, but admins should be able to enable the functionality.

            Sebastian Matheke added a comment - +1 This should be disabled after a sandbox copy, but admins should be able to enable the functionality.

            +1 !

            Térence LECROIX added a comment - +1 !

            Echoing Mark; org admins need the ability to toggle this flag in the sandbox environment (or even through the admin section).  Having incoming mail disabled as a default (with a warning) would be a viable workaround; the org/site admin would then be re-enabling incoming mail at their own risk if they haven't taken the appropriate precautions.

            Chris Rogers added a comment - Echoing Mark; org admins need the ability to toggle this flag in the sandbox environment (or even through the admin section).  Having incoming mail disabled as a default (with a warning) would be a viable workaround; the org/site admin would then be re-enabling incoming mail at their own risk if they haven't taken the appropriate precautions.

            +1 PCS-163430
            I need to test some mail related functionality so it is necessary to have the puller re-enabled in Sandbox.

            As per self hosted where admins have access to the JVM args to undo this - there should be an equivalent function to re-enable the mail puller on Cloud.
            Having to contact support each time after a clone is a waste of my time and Atlassian Support team's time.

            Cloud Site Admins should understand that after a clone the production mail handlers are also cloned along with the data and should be removed before enabling any incoming mail,  then a test mailbox should be attached instead.
            Perhaps a specific warning mentioning this should be shown instead of the System Flag/JVM args warning (which is completely irrelevant to admins now in Cloud).

            Mark Benson added a comment - +1 PCS-163430 I need to test some mail related functionality so it is necessary to have the puller re-enabled in Sandbox. As per self hosted where admins have access to the JVM args to undo this - there should be an equivalent function to re-enable the mail puller on Cloud. Having to contact support each time after a clone is a waste of my time and Atlassian Support team's time. Cloud Site Admins should understand that after a clone the production mail handlers are also cloned along with the data and should be removed before enabling any incoming mail,  then a test mailbox should be attached instead. Perhaps a specific warning mentioning this should be shown instead of the System Flag/JVM args warning (which is completely irrelevant to admins now in Cloud).

            WPG added a comment -

            Using the Import Jira Cloud on a Production site will also cause this issue.

            WPG added a comment - Using the Import Jira Cloud on a Production site will also cause this issue.

              jpitt@atlassian.com jaikibpitt
              44981f7279ac Greice Faustino (Inactive)
              Votes:
              54 Vote for this issue
              Watchers:
              63 Start watching this issue

                Created:
                Updated: