Option to enable "bypassRules" for Azure DevOps integrations

What is the challenge?

ADO projects can have work items rules in place that prevent the Aha integration from working. For example, the ADO state transitions may be restricted by values in other fields.

What is the impact?

In order to prevent the record sync from erroring out, Aha users either need to go to ADO to address the relevant prerequisites, or the Aha workspace needs to have automations, custom layout/fields, and/or custom workflow with fixed transitions so that the rule logic is mirrored between systems.

This is a lot of overhead that needs to be managed by Customization admins in Aha (account-wide impacts) that are usually not admins of, much less have access to, the ADO projects where the state rules exist.

Describe your idea

Aha users who are configuring integrations with ADO should have an option to enable "bypassRules" - which would eliminate the need for over configuring their Aha workspace to meet ADO's UI requirements.

When this option is selected, Aha's REST calls to ADO should set the bypassRules parameter to True (https://learn.microsoft.com/en-us/azure/devops/organizations/settings/work/rule-reference?view=azure-devops&tabs=inheritance#bypass-rules)