Which connector?: Jira Cloud connector (affects all Jira Cloud connectors using "Selected Projects" scoping 

Additional details:

Since a recent change (feature flag rolled out ~7/9 UTC, noted in the May 2026 release notes), Fivetran now syncs archived Jira projects into the PROJECT table by default, regardless of whether they're chosen in "Selected Projects." Fivetran Support confirmed this is intended behavior (ticket #396364).

This creates two problems for us:

1. Duplicate records — we run multiple Jira connectors, each scoped to a subset of projects for access-management reasons. Archived projects can share project IDs with projects actively synced by other connectors, so they show up as duplicates downstream.
2. Access management is defeated — the whole reason we scope connectors to "Selected Projects" is to control which projects' data lands in tables that specific teams/groups can query. Archived projects syncing in regardless of that scoping means users can see project data they were never meant to have access to.

The archived, archived_date, and archived_by_id columns let us filter/dedupe after the fact, but don't prevent the rows from syncing into the landing tables in the first place — which is the core issue for access management.

Requested feature: A setting to exclude archived projects from sync entirely, or alternatively, have archived projects respect the same "Selected Projects" scoping that applies to active projects.