GitHub Integration - Support Field-Based Filtering for Webhook Sync

What is the challenge?

The GitHub integration has no way to filter what syncs into Aha at the point of connection. Every issue in the selected GitHub project/repo flows in, with no way to scope the sync to specific criteria. Related filtering already exists elsewhere in our Aha! setup — the Jira integration supports a webhook-level filter, and Aha's GitHub import feature supports filtering by label — but the live GitHub integration lacks any filtering at all, and even where filtering exists elsewhere, it's limited to a single field (label/tag).

What is the impact?

• Teams are stuck manually curating what lands in Aha after the fact (e.g., marking "approve new records before importing" and reviewing each one) instead of configuring a rule once and letting it run.

• GitHub's structure is inherently more open and fluid than Jira's — many repos, no enforced hierarchy. Scaling the integration without filtering means more noise, more manual cleanup, and more risk of irrelevant records cluttering workspaces.

• Tying filtering to a single field (label) is itself a constraint — teams may need to scope syncs by status, issue type, custom field value, or other attributes already available in the field mapping, not just tags. A label-only filter would just move the limitation rather than remove it.

• Left unaddressed, it undermines confidence in scaling the GitHub integration to additional workspaces, since each new one inherits the same manual-curation burden.

Describe your idea.

Add filtering to the GitHub integration's webhook based on any field already available in the field mapping — not limited to tags/labels. Integration owners should be able to configure a filter once at setup (e.g., "only sync issues where status = X" or "only sync issues of type Y"), using whatever fields are already exposed in the mapping, rather than being restricted to a single filter mechanism.