The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Alert time ignoring when integration assigned to the specific team

sergii_yelenski
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 27, 2022

I created New Relic integration and assigned it to the specific team.

image.png

Then I created global alert policy and specified alert time to receive alerts during working hours.

image.png

But with the current settings my team continue receiving alerts during non-working hours.

When I deleting assigned team from the integration settings and adding it as responder team in the alert policy, all works as expected.

Is that a normal behaviour?

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Nick Haller
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 27, 2022

Hi @sergii_yelenski ,

Alert policies cannot control the creation of an alert based on the time. They are used to modify an alert such as increase the priority, add tags, add responders, etc.

Closest thing to this behavior would be to configure a notification policy under your team instead. These can delay / suppress alerts during the times you shared in your previous screenshot. They also have functionality to auto-close alerts if that is desired as well.

sergii_yelenski
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 27, 2022

Hi @Nick Haller,

Thank you for your answer! I've tried to configure notification policies instead and now it works like a charm.

Like Nick Haller likes this
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events