Skip to content

[feature] Ignored text should be clearly identified in alerts #3186

Open
@dtrezubSV

Description

@dtrezubSV

Version and OS
Paid subscription, v0.49.15

Is your feature request related to a problem? Please describe.
When viewing a change report (diff), all changes are shown using red and green colors, even the ones that match existing "Ignore" rules. This makes it hard to tell which changes were important (and caused a notification) and which ones were ignored.

Expected Behavior
Changes that match "Ignore" rules should be shown in a different way than regular changes.

Describe the solution you'd like
Here are some acceptable ways to display ignored changes:

  • Use lighter shades of red and green for ignored changes.
  • Or, use a strike-through effect on ignored changes.
  • Or, hide ignored changes completely from the diff.

The goal is for the user to easily see which changes caused a notification and which ones didn’t.

Describe the use-case and give concrete real-world examples
I have many Ignore rules. When I receive a notification, I don’t know which changes triggered it. I have to manually check each change against my rules. This is time-consuming and defeats the purpose of setting up Ignore rules.

Additional context
This would also help me see if any Ignore rules are broken or not working as expected.


✅ Acceptance Criteria
Scenario 1: Ignored change is included in diff view

Given a change that matches an "Ignore" rule
When the diff report is generated
Then the change should appear in the diff
 And it should be visually different from normal changes (e.g., lighter red/green or strike-through)

Scenario 2: Ignored change is excluded from diff view (optional feature)

 Given a change that matches an "Ignore" rule
   And a setting called "Hide ignored changes" is enabled
 When the diff report is generated
 Then the ignored change should not be highlighted in the diff at all

Scenario 3: Notification clarity

 Given a diff that includes both ignored and non-ignored changes
 When a notification is sent
 Then only the non-ignored changes should be considered the trigger
   And it should be clear which changes triggered the notification

Scenario 4: Debugging rules

 Given that a change appears in the diff as a normal red/green item
 And it does not match any Ignore rules
 Then the user should understand this change was not ignored
   And this can help the user debug or improve their Ignore rules

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions