Last modified by Boris Folgmann on 2025/05/09 14:06

From version 1.2
edited by Boris Folgmann
on 2025/05/09 12:40
Change comment: There is no comment for this version
To version 1.1
edited by Boris Folgmann
on 2025/05/09 12:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,8 +3,4 @@
1 -(% class="box warningmessage" %)
2 -(((
3 3  DRAFT
4 -)))
5 5  
6 6  * Attlassian 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.
7 7  * 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.
8 -* 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.