feat(aci): add issue category data condition

[ameliahsu]

this is a legacy condition that we still have to account for due to migrated workflows

[cursor]

Bug: Missing Default Comparison Causes Runtime Errors

The ISSUE_CATEGORY data condition entry in dataConditionNodesMap is missing a defaultComparison property. Without it, IssueCategoryDetails and IssueCategoryNode components attempt to access condition.comparison.value when condition.comparison is undefined for new conditions, leading to runtime errors. A defaultComparison (e.g., {value: GroupCategory.ERROR}) should be added, consistent with other configurable conditions.

static/app/views/automations/components/dataConditionNodes.tsx#L159-L167

sentry/static/app/views/automations/components/dataConditionNodes.tsx

Lines 159 to 167 in 7bc2309

	],
	[
	DataConditionType.ISSUE_CATEGORY,
	{
	label: t('Issue category'),
	dataCondition: IssueCategoryNode,
	details: IssueCategoryDetails,
	},
	],

static/app/views/automations/components/actionFilters/issueCategory.tsx#L31-L33

sentry/static/app/views/automations/components/actionFilters/issueCategory.tsx

Lines 31 to 33 in 7bc2309

	category:
	GROUP_CATEGORY_CHOICES.find(choice => choice.value === condition.comparison.value)
	?.label || condition.comparison.value,

static/app/views/automations/components/actionFilters/issueCategory.tsx#L42-L43

sentry/static/app/views/automations/components/actionFilters/issueCategory.tsx

Lines 42 to 43 in 7bc2309

	name={`${condition_id}.comparison.value`}
	value={condition.comparison.value}

Fix in Cursor

---

Was this report helpful? Give feedback by reacting with 👍 or 👎