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

[Piotr Nowak]

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. 

[Bill Sheboy]

Hi @Piotr Nowak 

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

• If so, you could use smart value, list filtering with the single lookup inside of the branch to do this, with a filter for each project: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588
• If you do not have a defined list of projects, I do not believe this is possible with current rule features.  There is no "group by" feature of automation lists, or nested branching.

Kind regards,
Bill

[Michael Wohlgemuth]

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:

[Piotr Nowak]

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]

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.

Result is:

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.

[YY Brother]

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哥