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 am building a Jira automation rule to send a scheduled email with the results from a JQL query. I currently have the email body formatted as such:
The following issues are due soon:
{{#issues}}
<li> <a href="{{toUrl}}">{{key}} - {{summary}}</a> is due on: <b>{{duedate.format("MM/dd/yyyy")}}</b></li>
{{/}}
which loops through the issues from the JQL query. However, this loops through ALL issues in the query results and sends the email to:
1. All assignees as a group email (if option "Process all issues produced by this trigger in bulk" is selected in the "Scheduled" options)
or
2. Each assignee individually, but with each issue in a different email (if option "Process all issues produced by this trigger in bulk" is not selected in the "Scheduled" options)
What I would like is for each assignee to get only one email with all issues in a list. The email should only send to each assignee individually, not as one email with multiple recipients.
Thanks!
Hi @ND
Instead of using Automation, can I suggest 3 easier ways to let users know about approaching due dates?
First, create a JQL filter + save your filter. Edit filter details: update permissions to make sure users can use it. Add an explicit filter name and filter description. Then :
What do you think about these suggestions?
@ND I think you are best off going with Sedera's approach. In Automation we have no way of grouping by a user or iterating over a list of users (then running a JQL for them).
@Sedera Randria approach is how I do in my team.
Cheers,
Nick [Atlassian - Automation Group Product Manager]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, I can't make a loop and I don't get why...
The mail I receive is empty, no datas at all :\
I do have ONE issue in a active sprint for my test, but can't figure out how to make my code work
<ol>
{{#issues}}
<li> [{{key}} {{summary}}]({{toUrl}}) was transitioned to {{status.name}} </li>
{{/}}
</ol>
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.