Changes for page Connect Jira with Microsoft Teams

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -11,10 +11,14 @@
11	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	+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:
14	14
15		-* 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.
16		-* The created workflow consists out of three steps and looks like this:
17	17	[[image:1774014880860-303.png||data-xwiki-image-style-border="true"]]
18		-* The domain name of the Webhook URL 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.
19		-* It can happen, that the JSON snippet provided by Atlassian for posting the card needs to be adapted. 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, if you get an error about it when saving the workflow.
20		-* The design of the adaptive card can be improved by changing the JSON in the last workflow step. [[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]].
	18	+
	19	+1. The wil wildcard expression [[https:~~/~~/*.environment.api.powerplatform.com/*>>url:https://*.environment.api.powerplatform.com/*]](((
	20	+domain name of the Webhook URL 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. Usally the
	21	+
	22	+)))
	23	+1. It can happen, that the JSON snippet provided by Atlassian for posting the card needs to be adapted. 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, if you get an error about it when saving the workflow.
	24	+1. The design of the adaptive card can be improved by changing the JSON in the last workflow step. [[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]].