You should have the latest Core fix installed (in both 8.0 or 8.2 versions) that will resolve your issue… Below is the content from Fix readme…
[i]PIE-22651 (IS_8.2_SP2_Core_Fix3)
The Server > Scheduler page displays tasks for all servers that share the same ISInternal functional alias.
When multiple Integration Servers have their ISInternal JDBC Pools configured to use the same database, the Server > Scheduler page shows all tasks for all servers, even those tasks that will only run on other servers. To improve how Integration Server Administrator displays these scheduled tasks, new functionality is introduced with this fix.
When viewing scheduled tasks, you can now use the Hide Remote Tasks filter to view only the tasks that can run on the current server. This includes tasks that are targeted to run on all servers, any server, and the current server. Tasks that are targeted to run only on other servers are not displayed.
To use this filter, click Filter Services on the Server > Scheduler page, then select Hide Remote Tasks and click Submit.
When scheduling a task, you can now use the Target Node parameter to schedule a task for All Servers, Any Server, or the current Integration Server in a non-clustered or clustered environment. In a non-clustered environment, other servers that use the same ISInternal database are not listed as targets that you can select for the task. For clustered environments, the Target Node parameter behaves the same as and replaces the Cluster Target Node parameter. That is, it lists Any Server, All Servers, and each Integration Server in the cluster. You can schedule a task to run on any of these options. This parameter is available on the Server > Scheduler
Create Scheduled Task page.
Note that when filtering out tasks scheduled for other servers, Integration Server uses the value specified by the
watt.server.scheduler.logical.hostname parameter. If a value is not specified, the server uses the host name. If you change this value after creating tasks, filtering will not work consistently. To correct this, change the Target field on the existing tasks to match the value of the watt.server.scheduler.logical.hostname parameter.[/i]
-Senthil