Problem with CRON and webhook Teams

Dąbrowski Damian April 16, 2024

Hi everyone, 

i have problem with Schedule Trigger with CRON. 

When used smart values in Teams webhook i didn't receive data from issues

Please, look to my prt sc. 

Screenshot 2024-04-17 085545.pngScreenshot 2024-04-17 085536.png

3 answers

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 17, 2024

Hi @Dąbrowski Damian 

Are you trying to send the message for the newly created issue?

If so, please add a branch to the rule.  Otherwise the rule cannot "see" the issue.

  • trigger: scheduled
  • action: create the task
  • branch: to most recently created issue
    • action: send the Teams message

Kind regards,
Bill

0 votes
Dąbrowski Damian April 17, 2024

Screenshot 2024-04-17 103453.png

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 17, 2024

Hello @Dąbrowski Damian 

What are the details from the Audit Log for the rule execution?

Is the rule running when you expect it to run?

Does the Audit Log indicate the rule executed and that the steps in the rule were executed?

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 17, 2024

Based on the Audit Log information, the rule is running and it has executed the action to send the message.

Did you follow the instructions for creating an incoming webhook, and use that in the rule action?

https://support.atlassian.com/cloud-automation/docs/use-automation-with-microsoft-teams/

Dąbrowski Damian April 17, 2024

Of course @Trudy Claspill

That's my announcement in Microsoft Teams. I used markdown. 

Issue: **{{issue.key}}**: {{issue.url}} <br>
Reporter: **{{issue.reporter.displayName}}** <br>
Status: **{{issue.status.name}}**

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events