#Alert Issue

4 messages · Page 1 of 1 (latest)

agile cloud
#

I think I have an issue with alerts.
I configured the alert to trigger when any new issue or event is created.
However, during testing, I noticed that the alert is not triggered when a new issue is created.
It only triggers when the issue receives more than one event (i.e., event count > 1).

Is this expected behavior? How can I make sure alerts are triggered immediately when a new issue or event is created?

slate deltaBOT
#

Hi @agile cloud. I'm happy to dig into this for you! I'll check my internal sources for answers to your question! :wave:

#

Based on the information in the knowledge sources, the behavior you’re experiencing is not expected if your alert is configured correctly.

Expected Behavior:
If you want an alert to trigger immediately when a new issue or event is created, you should configure your alert rule with either:

  • The "When" condition set to "A new issue is created", or
  • No "When" condition at all (which means the alert will trigger on every event).

Common Pitfalls:

  • If you combine "A new issue is created" with a frequency condition (like "number of events in an issue is more than X"), the alert will not trigger on the very first event, because a new issue by definition only has one event at creation. This is a common source of confusion and will prevent the alert from firing as you expect. For example, an alert with both "A new issue is created" and "number of events > 1" will never fire, because a new issue cannot have more than one event at creation. This is confirmed in several sources and GitHub issues, where users were advised to avoid combining these conditions for this reason Issue Alert Configuration Github Issue #41776.
#

What to do:

  • If you want an alert for every new issue, use only the "A new issue is created" trigger.
  • If you want an alert for every event, remove all "When" conditions.
  • Do not combine "A new issue is created" with frequency-based triggers (like "number of events in an issue is more than X") if you want immediate alerts for new issues.

If your alert is still not triggering as expected after following these guidelines, there may be an environmental or configuration issue (such as problems with worker processes or Kafka in self-hosted setups) Github Issue #85537 Github Issue #2510.

Let me know if you need help reviewing your specific alert rule configuration!

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: