The below documentation aims to present what happens to visibility of shared Scheduled Issues on a table, when certain settings are set and saved in particular manner.
Please access particular project (1) from the drop-down list and then head to "Project Settings" (2).
%20-%20accessing%20project%20settings.png?version=1&modificationDate=1546434434654&cacheVersion=1&api=v2)
Next, access "The Scheduler settings" as presented below (1):
%20-%20accessing%20the%20scheduler%20settings.png?version=1&modificationDate=1546435327672&cacheVersion=1&api=v2)
Finally, you are going to see the desired settings page, as presented below:
%20-%20Hide%20Inaccessible%20Scheduled%20Issues.png?version=1&modificationDate=1546436428524&cacheVersion=1&api=v2&width=837&height=250)
"Hide Inaccessible Scheduled Issues" feature is by default set on "Yes". This allows to keep unnecessary clutter away and is especially recommended in busy environments, where multiple of users deal with great number of scheduled issues.
If you turn this option to "No" and press save, then you can expect similar outcome in Scheduled Issues table, whilst being logged as a user with whom not all of the issues displayed are shared:
%20-%20Inaccessible%20Scheduled%20Issues%20set%20as%20visible%20for%20users%20with%20which%20SI%20is%20not%20shared.png?version=1&modificationDate=1546441778008&cacheVersion=1&api=v2)
In the above example, user is able only to "Execute" (1) a single issue, the one with whom it was shared with, as described here.