e-mail notification body for automation with projects name and issues id

Piotr Nowak April 25, 2024

Hello,

I've created automation "When a task is near due → send email reminder (3days)".

Rule runs great with e-mail body like below:

"

Hello {{distinctAssignee.displayName}},

The following issues are due within next 3 days:

{{#lookupIssues}}
<a href="{{url}}">{{key}} - {{summary}}</a>
{{/}}

Regards,

Jira Automation

"

I want however to add Project name before list of issues. To separate issues by projects like below:

"Project1 name:

-id1

-id2 

Project2 name:

-id1

-id2   ... etc 

 

Any Idea how to solve it? 

 

Regards. 

3 answers

0 votes
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 25, 2024

Hi @Piotr Nowak 

Do you have a known list of projects to group by? 

Kind regards,
Bill

0 votes
Michael Wohlgemuth
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 25, 2024

Perhaps you could use 2 lookups (one for each project) and store the results in a variable?

Never tried, so not sure, but it might work. Would roughly look like the following:

automation.PNG

Piotr Nowak April 25, 2024

Thank You for quick reply. 

This acctually might work to reach the target, however looks like a lot of setup and further supervision, especially with huge number of projects. I'm trying to find some more global solution. If there will be no other way, I'll go after your sugestion.

Michael Wohlgemuth
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 26, 2024

Depending on your automation version you could probably create a list at the start of the automation and then go through each entry in that list (say, of projectkeys) via the smart value branch.

screen_auto_2.PNG

Result is:

screen_auto_2_1.PNG

Which means, you can probably then use the JQL described earlier, but replace the project keys with {{p}} within the branch. Perhaps. Again, untested, all.

0 votes
YY哥
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 25, 2024

Hi @Piotr Nowak 

Welcome to our Community.

I am not sure about how to implement your requirement. What I did before for similar requirements is as follows. Maybe it can give your some hints.

Project1 name
Issue id1

Project1 name
Issue id2

Project2 name
Issue id3

Project2 name
Issue id4

JQL is ordered by project name field.

 

BTW, I may also prefer to using the email subscription of a jira filter to fullfill this requirement.

Thank,

YY哥

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events