Jira behaves differently on different version with using a same Element plugin

Issue Summary

A customer is using the plugin Elements connect external data fields to filter out the groups who can access issues in his project.
On reproducing in as below,

• the functionality works fine in v7.13 > User is able to access the issue if he is present in the group and able to see the issue when filtered using JQL as well.
• In 8.0 and above (tested in 8.5.10), user can access the issue successfully but the issue is not returned while running the JQL.

Steps to Reproduce

• Install Elements connect external data fields
• Create an Elements Connect Live Text (Legacy) custom field, plugged on the local datasource (SQL)
  Use this query: select group_name from cwd_group
  Key: 0
  Template: {0}
• Create a new project (with TEST as Key)
• Edit the Permission Scheme associated to this project
• Give the Browse Project permission only to the previously created Elements Connect custom field (i.e. remove default permission for logged in user)
• Put the field on all the project's screens
• Create a new ticket in this project (TEST-1)
• On the creation screen, select the "jira-administrators" group (in which your user is supposed to be)
• Browse to the issue navigator

Expected Results

The issue TEST-1 created above is visible in the JQL results

Actual Results

The issue TEST-1 created above is not visible

Workaround

The Jira in built group picker field works fine.