Configure ignore button for slack integration

[lukio3]

Problem Statement

On the slack integration as above, I want to be able to press ignore and know what version of 'ignoring' I am doing, is it:

• ignore forever?
• ignore until next occurance?

I have this granularity in the sentry web app, I would like the same in the slack integration

Solution Brainstorm

Add dropdown to ignore button on slack with some options (at least "ignore until next time")

[getsentry-release]

Routing to @getsentry/ecosystem for triage. ⏲️

[jonesphillip]

@lukio3 appreciate the feedback! Going to add this to the backlog, although we likely won't have the bandwidth to address this in the near term. Will keep this thread updated.

For anyone else looking at this, please 👍 this if interested and we will prioritize it higher.

[meysam81]

@BYK
Where should I look to change to fix this?

[JohnDuncanScott]

This is a super important feature even if it seems simple. For new users to the tool, the default Ignore functionality of "ignore forever" is, in my opinion, not something most teams would want and it's really easy to press and forget this. The Slack integration compounds this by not giving the other options. I've already had to undo permanent ignores multiple times and it's easy to forget. A step towards fixing this would be to change the label in Slack and the UI to "Ignore forever" / "Ignore permanently", as that makes it clearer and reduces human error. Many users seem to assume that the default Ignore just ignores it once. Adding the other options in Slack is then a bonus :). This current rough edge is also exacerbated by this bug: #24497 - so essentially the default Ignore functionality seems to break the state for an undetermined period of time.

[BYK]

@meysam81 that's a @manuzope question and I just pinged him now 😁

[manuzope]

Hi @meysam81, here's the line for the Ignore:

sentry/src/sentry/integrations/slack/message_builder/issues.py

Line 216 in dff2eb1

ignore_button = {"name": "status", "value": "ignored", "type": "button", "text": "Ignore"}

However, before you begin coding it up, it's worth discussing what you see as the solution so that we're not iterating at the time of the PR.

[meysam81]

@manuzope Thanks for your reply. Sure, I'll take a look and get back to you with how I plan to solve this in a day or two (a full-time job and a passion to contribute to open source has to be coordinated 😁 ).