[sentry-junior]

Adds a post-deployment data migration for the remaining schema-invalid DataCondition.comparison values tracked by ISWF-3455.

It normalizes only unambiguous integer, resolution, detector, and numeric priority values. Values that cannot be converted safely are logged and left unchanged. Existing named-priority cleanup from ISWF-3433 is not repeated.

This migration now follows 0120_replace_boolean_deescalation_comparisons, which already handles stored boolean de-escalation values, so this PR no longer duplicates that cleanup.

via Junior system actor event.

--

View Junior Session [Sentry]

[linear-code]

ISWF-3455

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/workflow_engine/migrations/0120_cleanup_invalid_data_condition_comparisons.py

for 0120_cleanup_invalid_data_condition_comparisons in workflow_engine

--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL

[kcons]

revisit this, and consider the migration(s) that have already gone through recently.

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/workflow_engine/migrations/0121_cleanup_invalid_data_condition_comparisons.py

for 0121_cleanup_invalid_data_condition_comparisons in workflow_engine

--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL

[kcons]

rebase please.

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/workflow_engine/migrations/0122_cleanup_invalid_data_condition_comparisons.py

for 0122_cleanup_invalid_data_condition_comparisons in workflow_engine

--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL

[getsantry]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀