You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have an integration set up between opsgenie and MS Teams (using the V2 integration type). Forwarding to teams has been setup and has been tested to work correctly.
However we would prefer to only forward notifications to teams when a note is added to the alert by a user. This only appears to work if we have already forwarded the alert created action for the alert as well (setup in screenshot below), but this can be noisy for our setup.
Is this a known dependency, that subsequent actions will only post if the original alert created event has also been forwarded? Or am I missing something?
Hi @Edward Rives ,
This is Darryl. I am here to help.
Understand that you would like to only push the alert data for a specific action is triggered without the alert creation to the Microsoft Teams channel.
Unfortunately, this is not feasible in the current design, the integration must push the alert creation to Microsoft Teams in prior to any other actions.
I have raised a feature request ticket on your behalf, OPSGENIE-150, however, all the feature request tickets don't provide public access, we will keep you posted.
Please note that our Product team reviews all Feature Requests (FR) together and they prioritize those with higher demand to be implemented first and any FR will take months until is ready since it needs to go through Design, Development, Testing, and rolling out to Production.
Hope this helps.
Support Engineer, Atlassian
Thanks for reaching out!
Your observation is right. Unfortunately, it is not currently possible to post other actions (like add note) if a create action is not sent first. We do have an internal ticket raised with the product team to explore this further. (reference ID: OGS-218)
Apologies for the inconvenience caused and Thank you for your understanding.