Skip to Content
Last modified by Boris Folgmann on 2026/03/20 15:29
From version 9.10
edited by Boris Folgmann
on 2026/03/20 14:09
Change comment: There is no comment for this version
To version 15.1
edited by Boris Folgmann
on 2026/03/20 15:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,8 +6,3 @@
1 -(% class="box warningmessage" %)
2 -(((
3 -DRAFT
4 -)))
5 -
6 6  1. Goto [[https:~~/~~/make.powerautomate.com>>https://make.powerautomate.com]] and make sure that the right environment is selected on the top right.
7 7  1. During the set-up of the workflow you will need to copy and paste a file which is different from language to language. Currently, these instructions have only a file for English and German language. Therefore, it makes sense, that you select one of these languages for the Power Automate UI. To do this, click on the cog icon on the top right and then on "View all Power Automate Settings"[[image:1746798531652-581.png||data-xwiki-image-style-border="true" height="333" width="399"]](((
8 8  Then select the wanted display language in the pop-up window and click on Save
... ... @@ -12,16 +12,11 @@
12 12  Use the menu on the left-hand side to go to the "My flows" page. Then click on "+ New flow" and select "Automated cloud flow" below "Build your own from blank"[[image:1746798851935-290.png||data-xwiki-image-style-border="true" height="346" width="668"]]
13 13  )))
14 14  1. Atlassian provides [[instructions how any project admin in Jira can use Jira Automation to post e.g. freshly create Jira issues in a MS Teams chat>>url:https://confluence.atlassian.com/automation/use-automation-with-microsoft-teams-993924683.html]]. The Jira Automation version which is part of all DevOps-as-a-Service installations is newer than 9.0.0, therefore you have to follow the instructions in which the Webhook URL is first copied into a secret key before it can be used in an automation rule.
15 -1. The created workflow consists out of three steps and looks like this:
10 +1. The created workflow consists out of three steps and looks like this: [[image:1774014880860-303.png||data-xwiki-image-style-border="true"]]
11 +1. The wildcard expression [[https:~~/~~/*.environment.api.powerplatform.com/*>>url:https://*.environment.api.powerplatform.com/*]] which matches the Webhook URLs needs to be added to the Jira Allowlist. Disable "Allow Incoming", but enable "Allow anonymous users" for the entry. Since this can be only done by Jira Sysadmins, customers need to raise a service request in their support project to get it configured.
12 +1. For the Parse JSON step you can copy and paste the Schema provided at [[JSON-Schema.json>>https://prd.sdc.t-systems.net/bitbucket/projects/DEVOPSAAS/repos/devops-tools-ms-teams-connection/raw/jira/JSON-Schema.json]]
13 +1. The design of the adaptive card can be improved by changing the JSON in the last workflow step. Please try first the best versions we developed over time. Ignore browser parse errors, these files cannot be properly interpreted by browsers.
16 16  
17 -[[image:1774014880860-303.png||data-xwiki-image-style-border="true"]]
18 -
19 -1. The wildcard expression [[https:~~/~~/*.environment.api.powerplatform.com/*>>url:https://*.environment.api.powerplatform.com/*]] which matches the Webhook URLs needs to be added to the Jira Allowlist. Since this can be only done by Jira Sysadmins, customers need to raise a service request in their support project to get it configured.
20 -1. For the Parse JSON step paste the Schema provided at [[JSON-Schema.json>>https://prd.sdc.t-systems.net/bitbucket/projects/DEVOPSAAS/repos/devops-tools-ms-teams-connection/browse/jira/JSON-Schema.json]] It's more reliable than the one provided by Atlassian.
21 -1. It can happen, that the JSON snippet provided by Atlassian for posting the card needs to be adapted. It's the files pasted in the Code view tab. It uses multiple times the name "Parse_JSON" to refer to the previous step. In a German environment this needs to be changed to JSON_analysieren, or you will get an error about it when saving the workflow.
22 -1. The design of the adaptive card can be improved by changing the JSON in the last workflow step. Please try first the best versions we developed over time:
23 -
24 -* EN [[https:~~/~~/prd.sdc.t-systems.net/bitbucket/projects/DEVOPSAAS/repos/devops-tools-ms-teams-connection/browse/jira/AdaptiveCard.json>>https://prd.sdc.t-systems.net/bitbucket/projects/DEVOPSAAS/repos/devops-tools-ms-teams-connection/browse/jira/AdaptiveCard.json]]
25 -* DE [[https:~~/~~/prd.sdc.t-systems.net/bitbucket/projects/DEVOPSAAS/repos/devops-tools-ms-teams-connection/browse/jira/AdaptiveCard_de.json>>https://prd.sdc.t-systems.net/bitbucket/projects/DEVOPSAAS/repos/devops-tools-ms-teams-connection/browse/jira/AdaptiveCard_de.json]]
26 -
27 -[[https:~~/~~/adaptivecards.io/>>url:https://adaptivecards.io/]] documents the structure, [[https:~~/~~/adaptivecards.io/designer/>>url:https://adaptivecards.io/designer/]] offers an interactive designer application. See also [[Format cards in Teams>>url:https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-format?tabs=adaptive-md%2Cdesktop%2Cdesktop1%2Cdesktop2%2Cconnector-html]].
15 +* EN [[AdaptiveCard.json>>https://prd.sdc.t-systems.net/bitbucket/projects/DEVOPSAAS/repos/devops-tools-ms-teams-connection/raw/jira/AdaptiveCard.json]]
16 +* DE [[AdaptiveCard_de.json>>https://prd.sdc.t-systems.net/bitbucket/projects/DEVOPSAAS/repos/devops-tools-ms-teams-connection/raw/jira/AdaptiveCard_de.json]]
17 +* [[https:~~/~~/adaptivecards.io/>>url:https://adaptivecards.io/]] documents the structure, [[https:~~/~~/adaptivecards.io/designer/>>url:https://adaptivecards.io/designer/]] offers an interactive designer application. See also [[Format cards in Teams>>url:https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-format?tabs=adaptive-md%2Cdesktop%2Cdesktop1%2Cdesktop2%2Cconnector-html]].
© 2018-2026 T-Systems International GmbH