Victor Lyuboslavsky c6fc9ce89c Added Primo migration for failing policies automation. (#32515) ... Fixes #32160 # Checklist for submitter - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually ## Database migrations - [x] Checked table schema to confirm autoupdate - [x] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [x] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - New Features - Dedicated automations for “No team,” including failing policy webhooks and Jira/Zendesk ticketing, separate from global settings. - Policies without a team now use the default team automation configuration instead of global. - Chores - Database migration splits global vs “No team” policy IDs and copies applicable automation settings to the default team. - To enable this behavior, set FLEET_PARTNERSHIPS_ENABLE_PRIMO=1 before running migrations. <!-- end of auto-generated comment: release notes by coderabbit.ai -->		2025-09-04 10:12:27 -05:00
..
failing_policies.go	Added Primo migration for failing policies automation. (#32515)	2025-09-04 10:12:27 -05:00
failing_policies_test.go	Added Primo migration for failing policies automation. (#32515)	2025-09-04 10:12:27 -05:00