This is continuing on from JRA-29417, as it doesn't appear to be fixed. Customers are still having the issue.

The workaround is still the same, visit the Default Application Access page (or directly at https://instance/secure/admin/user/EditDefaultApplicationAccess!default.jspa if your instance is JIRA-only) and click "Update" to re-save the default access settings.