Improve Problem Analyzers for Deployments from Production Orgs into Sandboxes
Sandboxes don't contain certain objects and permissions in comparison to Production and they can't be added. I find this causes issues in our CI jobs that are deploying production orgs into sandboxes unless you add a lot of customization to filters.
Since filters on a CI job don't get reflected across other CI jobs (see: https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/38727925-separate-filters-for-ci-jobs-to-reflect-filter-edi) this can be a major pain to keep them in sync and keep up to date if someone activates a features in production (ex. DevHub - which creates ScratchOrg custom object that doesn't exist in sandboxes).
Currently, we have the below noted as causing issues in Sandboxes:
Profile Permission - EditBillingInfo
Profile Permission - ManageSandboxes
Custom Object + related profile permissions - ActiveScratchOrg
Custom Object + related profile permissions - NamespaceRegistry
Custom Object + related profile permissions - ScratchOrgInfo
Custom Application - standard__LightningInstrumentation
Profile: User Permission - EditBillingInfo
Profile: User Permission - ManageSandboxes
Profile: User Permission - Packaging2PromoteVersion
Certain Report types may rely on objects that don't exist in sandboxes (LightningUsageByBrowserMetrics)
If these were caught by a problem analyzer, then our CI jobs could run with standard filters (ex. select all objects) and minimize the customization of a given filter to support several CI jobs backfilling production into different tracks/sandboxes. Right now, we have to keep a long "exclude" regex and make sure our filters are correct across many jobs.