Skip to content

feat(aci): Add issue type filter to old alerts#108273

Merged
malwilley merged 5 commits intomasterfrom
malwilley/feat/add-issue-type-filter-to-old-alerts
Feb 24, 2026
Merged

feat(aci): Add issue type filter to old alerts#108273
malwilley merged 5 commits intomasterfrom
malwilley/feat/add-issue-type-filter-to-old-alerts

Conversation

@malwilley
Copy link
Member

Ref ISWF-1991

Depends on #108241 (merge that first)

We already has an issue type data condition for workflow engine. This adds an issue type rule filter and the compatibility code which translates between the old models and new.

CleanShot 2026-02-13 at 14 45 17@2x

@malwilley malwilley requested review from a team as code owners February 13, 2026 22:47
@linear
Copy link

linear bot commented Feb 13, 2026

@malwilley malwilley changed the title feat(aci): Update issue type issue handler to work with frontend feat(aci): feat(aci): Add issue type filter to old alerts Feb 13, 2026
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Feb 13, 2026
@malwilley malwilley changed the title feat(aci): feat(aci): Add issue type filter to old alerts feat(aci): Add issue type filter to old alerts Feb 13, 2026
value = forms.ChoiceField(choices=list(TYPE_CHOICES.items()))


class IssueTypeFilter(EventFilter):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this so it shows up in the UI? (we aren't using these for processing anymore, so just want to confirm we need this class -- i could see it being needed for the legacy UI or because of API translation layers)

label = "The issue's type is {include} {value}"
prompt = "The issue's type is ..."

def _passes(self, group: Group) -> bool:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 since we're planning on deleting these filters, should we import the data condition evaluation and reuse that here to DRY up the code a little? (in general, i wouldn't recommend crossing app boundaries in that way, but since these are related and we're planning to delete this it might be nice to reduce the overhead of any updates / changes until we can clean everything up)

Base automatically changed from malwilley/feat/update-issue-type-issue-handler-to-work-with-frontend to master February 23, 2026 18:00
Copy link
Contributor

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

type_matches = group.issue_type == value
return type_matches if include_type else not type_matches

return False
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Boolean include option misinterpreted

Low Severity

include_type treats any non-"false" value as include, so if include is ever passed as a boolean False, the filter interprets it as include rather than exclude, producing the opposite result.

Fix in Cursor Fix in Web

@malwilley malwilley enabled auto-merge (squash) February 24, 2026 18:16
@malwilley malwilley merged commit b37d9f3 into master Feb 24, 2026
92 checks passed
@malwilley malwilley deleted the malwilley/feat/add-issue-type-filter-to-old-alerts branch February 24, 2026 18:24
@github-actions github-actions bot locked and limited conversation to collaborators Mar 12, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants