You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have an automation rule that works across all the issues linked to an epic. We are sending issue details to an external process via webhook. Using {{#issues}}{{key}}, {{/}} in the body of the web request I get a comma separated list of all the keys. If I run {{attachment.filename}} against ONE issue (different rule to test the smart value) I get a comma separated list of the attachments for that issue. What I would really like is a list of all the issue keys linked to the epic, and all the attachments associated with those issues. They don't even have to be associated pairs, I just need the values. I tried variations of:
{#issues}}{{key}}{{attachment.filename}}, {{/}}
{#issues}}{{key}}, {{attachment.filename}}, {{/}}
{#issues}}{{key}} {{#attachments}}{{filename}}, {{/}}
{#issues}}{{key}} {{/}}, {{#attachments}}{{filename}}, {{/}}
...
and to attempt just the file names:
{{attachment.filename}}
{#attachments}}{{filename}}, {{/}}
etc.
the best I got was a list of issue keys followed by a string of commas and spaces.
I found the answer -- {{#issues}}{{key}}_{{attachment.filename}} {{/}} produces string:
XXX-001_FileName1, FileName2, FileName3 XXX-02_FileNameX, ..., ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.