Last modified by Boris Folgmann on 2026/03/20 15:29

From version 16.1
edited by Boris Folgmann
on 2026/03/20 15:18
Change comment: There is no comment for this version
To version 14.1
edited by Boris Folgmann
on 2026/03/20 14:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,7 +8,7 @@
8 8  )))
9 9  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.
10 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:443/*>>https://*.environment.api.powerplatform.com:443/*]] 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.
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. 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 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 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.
14 14