I am trying to send a slack message via web request that asks to view the list of tickets that have not been touched in 7 days.
The same message sends with each issue that is found in the JQL query. I want one message and a list of tickets.
{{#lookupIssues}} *<{{url}}|{{key}}> {{/}} is not working.
Hi @Deanna Vazquez -- Welcome to the Atlassian Community!
Does your scheduled trigger have a JQL statement?
If so, the scheduled trigger will run the rule steps for each issue from the JQL. You may remove that trigger's JQL and only one message will be sent with the issues from the Lookup Issues action.
If you are concerned about sending an empty message (when no issues are found), you may add an Advanced Compare Condition after the lookup and before the message:
Kind regards,
Bill
I don't think I am following. The scheduled trigger does not have Run a JQL search and execute actions for each issue in the query checked.
This person is asking the same question but their screen has an option to processes in bulk as shown here
The only way I can produce the slack messages is by putting {{issue.summary}}: {{issue.url}}. I cannot put any other wording or it will repeat with every ticket link.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What version of Jira are you using: Cloud, Server, or Data Center?
Does your scheduled trigger have JQL at all? If so, please remove the JQL as it is not needed, regardless of the options selected for processing, bulk-handling, etc.
And, the bulk-handling feature for the scheduled trigger and branches is only available for Server and Data Center, and that is not needed for this type of rule.
To help confirm what is happening, please post an image of your audit log details showing the rule execution.
I am curious: why are you using a Send Web Request action to send the Slack message? All three versions of Jira automation rules have a built-in Send Slack Message action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The only way the rule is successful is with the below but then every issue has test in front of it but I want it to say:
Test
Ticket
Ticket
Ticket
Not
Test ticket
test ticket
test ticket
{
"message": "Test {{issue.summary}}: {{issue.url}}"
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Deanna, please see my earlier questions in the last post as they may help to improve your rule:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that info, Deanna!
Your rule and the audit log look okay, and based on the custom data for the Send Web Request action, the problem appears to be on the Okta side.
You can confirm this by copying the contents of that custom data, and writing it to the audit log with the rule's Log action. If it only shows your message text, "These tickets...", once, then the problem is in how the Okta webhook is processing the message.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.