Hi,
In automation for jira, we set up a webhook in order to communicatie with Teams in certain occasions. It works well, but the one that's not working like I would like is an automation that shows me a list of issues.
F.e. I want to receive a list of issues that are due today, I use this in automation:
{{#issues}}
• {{assignee.displayName}}: [{{key}} - {{summary}}] ({{issue.toUrl}})
{{/}}
We used slack before and it works perfectly, I receive a list with issues. But in Teams, I get 1 adaptive card per issue, instead of a list in 1 adaptive card.
Is it possible to have it all bundled in 1 adaptive card instead seperate cards per issue?
We're using Jira data center 9.16
Hi @ray
For a question like this, context is important for the community to help. Please post the following:
Until we see those...
You describe using the plural {{issues}} smart value, and thus I hypothesize you are using Jira Data Center and the bulk-handling feature of either the rule trigger or a branch. Is that correct?
If not, do you mean the smart value with the Incoming Webhook Trigger by supplying issues to the trigger? I believe that would process each issue from the trigger, one at a time. An alternative is to send the issues as custom data with the trigger, and then use the custom data to build a JQL expression for use with a Lookup Issues action...sending that in one message.
Kind regards,
Bill
Hi @Bill Sheboy
Thanks for your answer. So we're using Jira data center 9.16 and I set it up as a scheduled automation:
When it passes the issues, it recreates a new adaptive card per issue using the incoming webhook trigger.
But you gave me a good suggestion by using the Lookup-issues action. Then I can use the list-component to display a list:
{{#lookupIssues}}
* {{summary}}: <{{url}}>
{{/}}
The only problem I'm having is, that it shows the summary and the url. I would like to achieve that it only displays a clickable summary. So that we can go to the url directly instead of displaying the long url behind the summary.
I tried many things, the best thing I could achieve is using <> for the url so it's clickable. But I would like to have a cleaner look with only a clickable summary...
I tried a href HTML, <{{url}}|{{summary}}> but no luck so far
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For a hyperlink, the markup of where you are sending the information matters. That is: what is the supported format for the message? For example with HTML:
<a href="{{url}}">{{summary}}</a>
I recommend researching that first, and then creating a test rule to add a single hyperlink with the correct markup. Once that works, try the same markup with your complete 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.