fe7ce902b27f - I can confirm this works for me now. Thank you for your attention to this issue.

Sorry adamru, but please read exactly what is stated in that announcement. Jira Server is no longer supported by Atlassian. Jira Data Center is still fully supported beside of Jira Cloud. If you have other information, please join these with us. Otherwise please do not create rumors! If so that should be the job of Atlassian itself

aefc4c4c1923 ... hasn't all support ended for DC?

https://www.atlassian.com/migration/assess/journey-to-cloud

Support for Server products ended on Feb. 15, 2024

Server products and apps no longer receive technical support, security updates, and bug fixes for vulnerabilities.

fe7ce902b27f - It have not been "Fully" rolled out - You forgot your Datacenter customers(again!).

https://jira.atlassian.com/browse/JIRAAUTOSERVER-1045 - Still "Gathering Interest"....OMG! - Teams on DC is broken = Incident!

Even the lovely 1st level supporters on keep just pasting wasteless updates of "since apologies" and "sorry for the inconvenience".

We reported this incident as a customer on July 16th - And still almost 2 months later, not a single valuable update on progress towards resolution.......All while Cloud customers are serviced.

Hi all,

We're noticed that some rules have been saved using the new url but with the old version of the MS teams action. We have added a check to pick this up and log it as an error in the audit log. The new changes have now fully been rolled out and this issue should no longer occur. However, if you are experiencing issues still, please check whether your rule has been updated.

The error message in the audit log will appears as follows: 

Thank you for your patience in this. 

62534117e636 / ezhapa / 89403358cf11 - the integration between Jira automations and MS Teams via Workflows is still broken. Who is responsible for re-opening this ticket and continuing to work the problem?

00a9560cfd34 exactly.

89403358cf11  please reopen this issue until the fix.

Thank you.

fae241a7c16d - it's not the community's responsibility to find a solution for that error. The Atlassian team – ezhapa and 89403358cf11 , et al. – is supposed to provide to the community an integration that doesn't throw that error. They claimed to have published an update but it's obviously still broken. This ticket obviously still needs to be worked. There are 154 people watching this issue and hoping Atlassian can solve its problems.

249cc3084ccd is it working for you?

89403358cf11 

What about Datacenter Customers?!?

I reported the breaking change/bug more than a months ago - And not a single update to the ticket:

https://jira.atlassian.com/browse/JIRAAUTOSERVER-1045

It's not even linked to this Cloud ticket - Typical Atlassian to constantly down-prioritize DC customer(Which cannot go to Cloud)

Currently the MS Teams integration to Jira/Confluence DC is BROKEN - You cannot create new automations, and the eixsting integrations seize to work in December!

Thanks for the update 89403358cf11  - appreciate it. WIll get our automation rule owners to update it.

Thanks again

We have the same problem: ""ExpressionEvaluationFailed. The execution of template action 'Send_each_adaptive_card' failed: the result of the evaluation of 'foreach' expression '@triggerOutputs()?['body']?['attachments']' is of type 'Null'. The result must be a valid array.""

Dear 89403358cf11 ,
It doesn't work for me either.
The automation rule is succesfully sending the Webhook request but in MS Teams workflow, this error appears:

"ExpressionEvaluationFailed. The execution of template action 'Send_each_adaptive_card' failed: the result of the evaluation of 'foreach' expression '@triggerOutputs()?['body']?['attachments']' is of type 'Null'. The result must be a valid array."

Hi Charlie Gavey I tried the same, but it's not working. Getting the below error msg:

I used the below Jira automation for testing:

We’ve just shipped an update to the ‘Send Microsoft Teams message’ action in Automation. The action now uses Workflows in Microsoft Teams to send messages from your automation rules.

To update your rules, follow these steps:

1. Go to your channel in Teams and select …› Workflows > Post to a channel when a webhook request is received
2. Paste the webhook URL into the ‘Send Microsoft Teams message’ action
3. Select Update.

We recommend you do this by December 31, 2024, to avoid any interruption to your automation rules.

https://community.atlassian.com/t5/Automation-articles/Update-on-sending-Microsoft-Teams-messages-with-Atlassian/ba-p/2780258

Hi all,

We’ve just shipped an update to the ‘Send Microsoft Teams message’ action in Automation. The action now uses Workflows in Microsoft Teams to send messages from your automation rules.

To update your rules, follow these steps:

1. Go to your channel in Teams and select …› Workflows > Post to a channel when a webhook request is received
2. Paste the webhook URL into the ‘Send Microsoft Teams message’ action
3. Select Update.

We recommend you do this by December 31, 2024, to avoid any interruption to your automation rules.

https://community.atlassian.com/t5/Automation-articles/Update-on-sending-Microsoft-Teams-messages-with-Atlassian/ba-p/2780258

Hi all, we've shared an update to Community here - we'll be releasing an update to the MS Teams component within the next few weeks: https://community.atlassian.com/t5/Automation-articles/Update-on-sending-Microsoft-Teams-messages-with-Atlassian/ba-p/2780258

Hi all, just a quick note to confirm that the Automation Platform team is working to implement a new Microsoft Teams action, as an alternative to the current action that relies on the soon-to-be deprecated connectors. We'll provide an update shortly with more info on timelines for this new action.

This is not a fix to the issue but I have had success with this workaround using the 'Send Web Request' action and using basic JSON.  A bit messy but does the job.  See link below:

https://community.atlassian.com/t5/Jira-Service-Management/Transition-to-MS-Teams-Workflows/qaq-p/2749257

A second option is to use the action 'Send an email' and use the Teams channel email address.   Again a messy option, but an option.

Hi Rebecca, is your comment also true for the corresponding Data Center Ticket JIRAAUTOSERVER-1045, as we as Data center Customers have the same for a solution to the new complex webhook concept from MS PowerAutomate Workflows instead of the current O365 Webhooks.

If so please also provide the same comment on the Data Center Ticket. Otherwise please inform us also, because then we as Data Center customers will also further escalate  JIRAAUTOSERVER-1045

Hi everyone,

Thank you for bringing this issue to our attention and for your patience as we work on it. We understand the importance of this feature and want to reassure you that our team is actively investigating the problem described in this ticket.

Our engineers are currently analyzing the root cause and exploring potential solutions. We are committed to resolving this as quickly as possible and will keep you updated on our progress.

In the meantime, if you have any additional information or specific use cases that could help us in our investigation, please feel free to share them here.

Thank you for your understanding and continued support.

Best regards,
Atlassian Team

https://jira.atlassian.com/browse/JIRAAUTOSERVER-1045

Does anyone know if there is a ticket for the Data Center?
 

a7e9ce396f68 Yes, it's clear now.
Thank you.

Hi Konstantinos,

I don't know how to be cleared on what happens when we as a enterprise company send a email to a external email address (and as mentioned the teams channel email address is a external email address).

We as enterprise company on mail server level ad many information's, like legal disclaimers and other stuff to any email body of any email that is send to a external email address.

So the complete large email body with the above mentioned stuff would be then posted to the teams channel and not only the email body that we would create with automation.

Hopefully this makes clearer why your workaround is no suitable workaround for us as enterprise company.

Sorry Konstantinos, but that is not really a workaround. Do you know how long disclaimers mails send to externals (and the teams channel mailbox will definitely by external from the standpoint of our Exchange Server) are. this would fill up the channel with useless and confusing information , while the really important information threatens to get lost in the amount of information written into the channel by email in.

We need this on Data Center asap! 

A solution for this issue is vital. Please check asap. 

+1

Also, this feature needs to be released for Jira Data Center as well.

+1

Meanwhile Microsoft informed on their official Blog entry https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ for this retirement, that they have removed the information from the footer of connector posted cards. But this does not change anything to their retirement plans at all.

That means Atlassian should hurry up to get a support for the new PowerAutomate Workflows that Microsoft defined as replacement of the O365 webhooks.

As we all know that Microsoft is not taking care of any frustrated users we can't expect any change to their planned time schedule.

Currently Microsoft is hit by a shitstorm on there short-notice announcement of retirement of their O365 Webooks (see here for the shitstorm on the request to step back from their retirement plans https://feedbackportal.microsoft.com/feedback/idea/80ed6877-b642-ef11-b4ad-000d3a7aba8b )

Also since yesterday the announcement is no longer pop up when a O365 webhook is creating a chat entry in a teams channel it was the case in the last days before yesterday. So maybe Microsoft is already thinking about a longer or changed retirement plan.

But nevertheless Atlassian should work on providing an additional Automation Action that is able to use the (new) MS PowerAutomate Premium Workflow Webhooks that need another payload as the current O365 webhooks. Or th eoption to choose in the current Automation action if the target is O365 WEbhook or a Workflow Webhook.

Hi,

So not to put any pressure, BUT from Microsoft:

Wave 1 – effective August 15th, 2024: All new Connector creation will be blocked within all clouds

Wave 2 – effective October 1st, 2024: All connectors within all clouds will stop working

Should this not warrant a higher priority.  We depend very heavily on this automation functionality.  I'm already cringing at the amount of work it will take to convert to whatever solution Atlassian comes up with OR worse creating JSON as in the community examples.

Susan

+1

We need to be able to trigger notifications from workflow actions apart from plain issue creation notoficaation. Ideally the message that is triggerd needs to be customizable.

BTW let me ask here if somebody find at MS some information about valid URL patterns for the new Workflow Webhook URL's?

Because we do not want to open complete  https://.azure.com/ in the Jira Allowlist we are really searching for a more specific valid URL pattern but up to now did not find such. Old  O365 connector URL was quite static with https://<tenant-name>.webhook.office.com but we can't find any tenant specific systematic in the new Workflow Webhook URL's like https://prod-244.westeurope.logic.azure.com:443/workflows/... or https://prod-180.westeurope.logic.azure.com:443/workflows/... 

Atlassian now has to show that they are as company partnering with Microsoft in a good way and provide a working solution. Because it is a fact that most of the enterprise companies are meanwhile using M365 in their daily work and wit that are using the Send Message to Microsoft Teams Action automation action to inform Teams Channels about configured Events on Jira side. As everybody in these companies having Teams active all the time channel notifications are the process to inform user groups about important events  and wit that trigger work on that events.

That means without a Atlassian Jira  DataCenter OOTB functionality to send information to Teams channels Business Processes in our companies would get broken.

So Please Atlassian fix this before MS will decommission the current O365 connectors and not as normal have such a bug open for several years.

This worked for me:
https://www.youtube.com/watch?v=2PDvEC9bnQ4

You don't get very many options for what qualified for notifications / posts in Teams but it does work. The 2 big gotcha's I would said it should be done with a service account in my opinion and it looks like it can only work in a public channel. 

We've also been hacking it out over here:
https://community.atlassian.com/t5/Jira-questions/O365-connectors-within-Teams-will-be-deprecated/qaq-p/2747544

For those looking for a workaround until this is fixed, there is a thread at Transition to MS Teams Workflows (atlassian.com) with some recommendations.

If someone figures something, can you share how you did it? I found a lot of marketing articles with a lot of buzz words but when I get into the the “how to’s” or technical pages I found from MS have lead to 404’s. I found this YouTube video that looks promising but can’t get Power Automate to connect to Jira Cloud:
https://www.youtube.com/watch?v=6KbP2BdsbCU

I’m trying to keep an open mind about this but it looks like there are a good amount of “known” issues and gotcha’s about this roll out so far:
https://learn.microsoft.com/en-us/connectors/jira/

Without this getting fixed, so many business processes are going to break.  I hope this is fixed before Microsoft turns off webhooks at the end of August.

This is very important. We rely heavily on Jira automations sending messages to Teams. This is our primary communication mechanism to our entire company about Jira activity.

Please provide support foe the new workflows. Our company relies on this integration.

+1
The MS Teams integration is now broken - Cannot do any new channel notifications - Existing MS Team notifications will stop to work by October 1st.

This applies to both Datacenter & Cloud products.

My stuff is so broke, please fix.

+1 this is really important for our organization to keep this feature functioning.

ezhapa  Add a due date to this issue plz: 2024-08-15 (see MS article in description)

We rely heavily on this functionality for our operations group and real time monitoring.  Can this be upgraded as to not be a suggestion as it is functionality that will be lost soon once this is deprecated?  Thanks!  

https://getsupport.atlassian.com/browse/CES-44364