Jira have outgoing connections even though disabled Analytics

Issue Summary

Jira have outgoing http connections even though disabled Analytics

Steps to Reproduce

1. Jira Administration > System > Analytics Disabled analytics
2. Restart Jira and see outgoing connection through forward proxy or debug outgoing connections

   172.20.0.5 - proxyuser [05/Dec/2019:05:13:11 +0000] "CONNECT btf-analytics.s3.dualstack.us-east-1.amazonaws.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
   ...
   172.20.0.5 - proxyuser [05/Dec/2019:06:13:14 +0000] "CONNECT server-notifications.atlassian.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
   172.20.0.5 - proxyuser [05/Dec/2019:06:13:14 +0000] "CONNECT server-notifications.atlassian.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
   

Expected Results

There is no outgoing connection related analytics if it's disabled.

Actual Results

• Every 6 hours, Jira sent request to server-notifications.atlassian.com to get latest news from atlassian.

  172.20.0.5 - proxyuser [05/Dec/2019:06:13:14 +0000] "CONNECT server-notifications.atlassian.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
  172.20.0.5 - proxyuser [05/Dec/2019:06:13:14 +0000] "CONNECT server-notifications.atlassian.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
  

  clusteredjob table

  id     job_id                                       job_runner_key                               sched_type  interval_millis  first_run      cron_expression  time_zone  next_run       version  parameters  
  -----  -------------------------------------------  -------------------------------------------  ----------  ---------------  -------------  ---------------  ---------  -------------  -------  ----------  
  18514  com.atlassian.whisper.plugin.fetch.FetchJob  com.atlassian.whisper.plugin.fetch.FetchJob  I           21600000         1575514489169  (null)           (null)     1575536715200  2        (null)      
  

• Jira sent request to btf-analytics.s3.dualstack.us-east-1.amazonaws.com when start Jira application to get hash code that is used for analysis

  172.20.0.5 - proxyuser [05/Dec/2019:05:13:11 +0000] "CONNECT btf-analytics.s3.dualstack.us-east-1.amazonaws.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
  

Workaround

Disable Analytics Client Plugin and Atlassian Notifications Plugin from Jira Administration > Add-ons > Manage add-ons > System add-ons

Please DO NOT disable Analytics Client Plugin if you have Jira Service Management installed. It will disable service desk reports plugin immediately.
Having the Analytics app disabled might affect jira Start up.