-
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.
[CLOUD-11243] Ability to enable Global Mail Settings - Email puller on Sandbox
| Description |
Original:
Currently, as mentioned here: [Manage product sandboxes|https://support.atlassian.com/organization-administration/docs/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 when 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. !image-2021-08-04-13-23-21-730.png! |
New:
Currently, as mentioned here: [Manage product sandboxes|https://support.atlassian.com/organization-administration/docs/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. !image-2021-08-04-13-23-21-730.png! |
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.
| Assignee | Original: Matt Tse [ mtse@atlassian.com ] | New: jaikibpitt [ jpitt@atlassian.com ] |
+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).
| Parent | New: CLOUD-10910 [ 1411141 ] | |
| Workflow | Original: JAC Suggestion Workflow 3 [ 4187441 ] | New: JAC Sub-task Workflow [ 4201398 ] |
| Issue Type | Original: Suggestion [ 10000 ] | New: Sub-task [ 6 ] |
| Status | Original: Gathering Interest [ 11772 ] | New: Open [ 1 ] |
| Component/s | New: Sandbox [ 62090 ] | |
| Component/s | Original: System - Mail Server - Incoming [ 63894 ] | |
| Key | Original: JRACLOUD-77154 | New: CLOUD-11243 |
| Project | Original: Jira Cloud [ 18514 ] | New: Atlassian Cloud [ 14613 ] |
| Assignee | New: Matt Tse [ mtse@atlassian.com ] |
+1
This should be disabled after a sandbox copy, but admins should be able to enable the functionality.